Re: [KJ] Re: [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked region

Am Dienstag, 5. Juni 2007 13:05 schrieb Yoann Padioleau:
> Ok. Do you have a preference on the format ?  a <file>:<line> format  ?
> 
> Is there a place that gathered all those implicit programming rules 
> (that copy_from_user must not be called inside a spinlock, etc) so that
> I can translate them in a script for our tool.

How much C does your tool understand? You might basically
test for code paths that go to "might_sleep()"

	Regards
		Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [KJ] Re: [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked region
    • From: Yoann Padioleau <[email protected]>

• References:
  • [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked region
    • From: Yoann Padioleau <[email protected]>
  • Re: [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked region
    • From: Andrew Morton <[email protected]>
  • Re: [KJ] Re: [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked region
    • From: Yoann Padioleau <[email protected]>

• Prev by Date: Re: [PATCH] atmel_serial: Fix break handling
• Next by Date: [PATCH] [RESEND] neofb: Fix pseudo_palette array overrun in neofb_setcolreg
• Previous by thread: Re: [KJ] Re: [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked region
• Next by thread: Re: [KJ] Re: [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked region
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]