linux-kernel - Re: [vfs] BUG: spinlock trylock failure on UP on CPU#0, swapper/0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131107151439.GO13318@ZenIV.linux.org.uk>
Date:	Thu, 7 Nov 2013 15:14:39 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	David Howells <dhowells@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [vfs] BUG: spinlock trylock failure on UP on CPU#0, swapper/0

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@...hat.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 ;-/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/