From: Al Viro <viro@ZenIV.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [vfs] BUG: spinlock trylock failure on UP on CPU#0, swapper/0
Date: Thu, 7 Nov 2013 15:14:39 +0000 [thread overview]
Message-ID: <20131107151439.GO13318@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20131107123031.GA27852@infradead.org>
On Thu, Nov 07, 2013 at 04:30:31AM -0800, Christoph Hellwig wrote:
> On Thu, Nov 07, 2013 at 08:10:42PM +0800, Fengguang Wu wrote:
> > Greetings,
> >
> > I got the below dmesg and the first bad commit seems to be
> >
> > commit 1247c74b4f3f3725a8bd8dc0bbd22baa2a9049ae
> > Author: David Howells <dhowells@redhat.com>
> > Date: Thu Sep 12 19:22:53 2013 +0100
> >
> > VFS: Put a small type field into struct dentry::d_flags
>
> Where is that commit coming from? I can't find any public mentioning of
> it, and big brother from Mountain View can't either.
It's vfs.git#for-next and it's messed up on cherry-picks; will put the
saner branch in a few.
Al, starting to share Linus' distaste for cherry-picks - crap like that
happens too easily ;-/
next prev parent reply other threads:[~2013-11-07 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 12:10 [vfs] BUG: spinlock trylock failure on UP on CPU#0, swapper/0 Fengguang Wu
2013-11-07 12:13 ` [vfs] [ INFO: possible recursive locking detected ] Fengguang Wu
2013-11-07 12:30 ` [vfs] BUG: spinlock trylock failure on UP on CPU#0, swapper/0 Christoph Hellwig
2013-11-07 12:34 ` Fengguang Wu
2013-11-07 15:14 ` Al Viro [this message]
2013-11-07 15:16 ` Christoph Hellwig
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=20131107151439.GO13318@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dhowells@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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