From: Al Viro <viro@ZenIV.linux.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Sachin Sant <sachinp@in.ibm.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, Ingo Molnar <mingo@redhat.com>,
peterz@infradead.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: Next April 24 : BUG: lock held at task exit time!
Date: Fri, 24 Apr 2009 15:04:45 +0100 [thread overview]
Message-ID: <20090424140445.GL8633@ZenIV.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0904241249180.20196@blonde.anvils>
On Fri, Apr 24, 2009 at 12:55:44PM +0100, Hugh Dickins wrote:
> Indeed, thanks for the headsup Stephen. My own config gives, not
> Sachin's message (or not still visibly on screen anyway), but an
> outright panic. Shame that leaked out into the big world, we'd
> all have preferred a quiet fixup! Here's a patch, which I'll
> also send as reply to the relevant thread.
Applied, will fold on reorder (since Ingo is asking for what will amount
to reorder anyway).
next prev parent reply other threads:[~2009-04-24 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 5:04 linux-next: Tree for April 24 Stephen Rothwell
2009-04-24 6:55 ` Next April 24 : BUG: lock held at task exit time! Sachin Sant
2009-04-24 7:55 ` Stephen Rothwell
2009-04-24 11:55 ` Hugh Dickins
2009-04-24 14:04 ` Al Viro [this message]
2009-04-24 14:11 ` Stephen Rothwell
2009-04-24 7:12 ` Next April 24: [S390] allmodconfig build failure (trace/events) Sachin Sant
2009-04-24 7:25 ` Ingo Molnar
2009-04-24 8:41 ` Heiko Carstens
2009-04-29 9:51 ` Sachin Sant
2009-04-29 11:51 ` Heiko Carstens
2009-04-29 12:04 ` Ingo Molnar
2009-04-29 12:09 ` Steven Rostedt
[not found] ` <20090424150456.ff35e4ea.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-04-24 17:56 ` linux-next: Tree for April 24 (p54 build error) Randy Dunlap
2009-04-24 20:47 ` linux-next: Tree for April 24 (p54 build error) (and pull request: wireless-next-2.6 2009-04-24) Christian Lamparter
[not found] ` <200904242247.15042.chunkeey-S0/GAf8tV78@public.gmane.org>
2009-04-30 18:30 ` John W. Linville
2009-04-26 13:20 ` linux-next: Tree for April 24 Benny Halevy
2009-04-27 4:21 ` Stephen Rothwell
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=20090424140445.GL8633@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=sachinp@in.ibm.com \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).