From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
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 07:16:34 -0800 [thread overview]
Message-ID: <20131107151634.GA15577@infradead.org> (raw)
In-Reply-To: <20131107151439.GO13318@ZenIV.linux.org.uk>
On Thu, Nov 07, 2013 at 03:14:39PM +0000, Al Viro wrote:
> 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 ;-/
I still haven't seen it on any mainlinglist..
prev parent reply other threads:[~2013-11-07 15:16 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
2013-11-07 15:16 ` Christoph Hellwig [this message]
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=20131107151634.GA15577@infradead.org \
--to=hch@infradead.org \
--cc=dhowells@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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