From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.29-rc3: BUG: scheduling while atomic: udevd/917/0x10000100
Date: Wed, 11 Feb 2009 09:49:49 +0100 [thread overview]
Message-ID: <1234342189.23438.113.camel@twins> (raw)
In-Reply-To: <20090211083217.GC21105@elte.hu>
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().
next prev parent reply other threads:[~2009-02-11 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 8:09 2.6.29-rc3: BUG: scheduling while atomic: udevd/917/0x10000100 Vegard Nossum
2009-02-11 8:32 ` Ingo Molnar
2009-02-11 8:49 ` Peter Zijlstra [this message]
2009-02-11 9:27 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1234342189.23438.113.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.