From: Jeff Dike <jdike@ka...> - 2001-08-13 13:05:43
> which basically means (AFAI can tell(!)) that a kmalloc was called on
> interrupt ctx without the atomic flag set.
> #### EITHER this is not interrupt ctx and the check in_interrupt() is
> #### borken.
There's nothing vaguely interrupt-like on that stack, so the in_interrupt
check fired for the wrong reason.
Have a look at irq_stat and see which of __local_irq_count and
__local_bh_count is non-zero.
Is this reproducable?
Get latest updates about Open Source Projects, Conferences and News.