On Tue, 17 Nov 1998, Karlis Peisenieks wrote:
> I guess this might be caused by calling kmalloc or functions which call
> kmalloc with wrong "priority" (not GFP_ATOMIC) what on turn can schedule
> in low memory situations (to let other jobs free memory).
>
> Correct me if I'm wrong :-)
I believe that kmalloc checks intr_count and will emit a diagnostic if you call
it with intr_count > 0 and without GFP_ATOMIC. It will also adjust itself
to the atomic behavior.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
