Re: 2.6.29-rc3: BUG: scheduling while atomic: udevd/917/0x10000100

From: Ingo Molnar
Date: Wed Feb 11 2009 - 04:28:16 EST



* Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> wrote:

> On Wed, 2009-02-11 at 09:32 +0100, Ingo Molnar wrote:
>
> > There's a fourth possibility:
> >
> > - Given that it's udevd that does it - maybe we leaked a softirq preempt
> > count in some rare sysfs file, and it did not get discovered until the
> > next innocent piece of kernel code preempted?
> >
> > But i thought lockdep would already warn if we exited a syscall with locks
> > held or with a preempt count elevated - Peter?
>
> From a quick look it only checks task->lockdep_depth, in lockdep_sys_exit().

That could be broadened then i guess - there's never a good excuse for exiting a
syscall with an elevated preempt count.

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/