On Wed, Aug 01, 2007 at 05:26:53PM -0700, Andrew Morton wrote:
> Why on earth is that using GFP_ATOMIC? This function later goes on to
> create procfs files and such things.
Seems fairly common in driver initialisation code. I removed three
instances of this in the advansys driver.
> y'know, we could have a debug option which will spit warnings if someone
> does a !__GFP_WAIT allocation while !in_atomic() (only works if
> CONFIG_PREEMPT).
>
> But please, make it depend on !CONFIG_AKPM. I shudder to think about all
> the stuff it would pick up.
Seems like you'd get a lot of false positives. How about a call:
slab_warn_about_atomic_allocs();
right before calling the initcalls, and then
slab_stop_warning_about_atomic_allocs();
after calling them? That should give people a lot to chew on for a few
months. Obviously, you would need to not warn about allocations from
interrupt context, as you say above.
--
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
-
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/
[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]
