linux-ext4 - Re: kernel BUG at fs/ext/super.c:428

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1231961377.14825.51.camel@laptop>
Date:	Wed, 14 Jan 2009 20:29:37 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
Cc:	Theodore Tso <tytso@....edu>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>,
	Nick Piggin <nickpiggin@...oo.com.au>
Subject: Re: kernel BUG at fs/ext/super.c:428

On Wed, 2009-01-14 at 11:16 -0800, Pallipadi, Venkatesh wrote:
> On Tue, Jan 13, 2009 at 08:40:59PM -0800, Theodore Tso wrote:
> > On Wed, Jan 14, 2009 at 02:48:13AM +0000, Arjan van de Ven wrote:
> > >> Well, Arjan's commit, efaee192: "async: make the final inode deletion
> > >> an asynchronous event", does change how inodes get deleted, and this
> > >> looks like a race where an inode is getting deleted during the umount.
> > >>
> > >> So I would try reverting commit efaee192 and see if it fixes things
> > >> before starting a full bisect...
> > >
> > > the commit is already reverted before rc1
> > >
> > 
> > Ah, right.  I see, the async infrastructure is still in fs/super.c,
> > but the actual code to insert deleted inodes onto the s_async_list was
> > removed in commit b32714b.  Sorry, that confused me.
> > 
> > OK, so assuming that Venkatesh was using something post-rc1, I can't
> > suggest anything other than a full bisect.  Sorry....
> > 
> 
> Below is the result of full bisect
> 
> 38d47c1b7075bd7ec3881141bb3629da58f88dab is first bad commit
> commit 38d47c1b7075bd7ec3881141bb3629da58f88dab
> Author: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> Date:   Fri Sep 26 19:32:20 2008 +0200
> 
>     futex: rely on get_user_pages() for shared futexes
>     
>     On the way of getting rid of the mmap_sem requirement for shared futexes,
>     start by relying on get_user_pages().
>     
>     Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
>     Acked-by: Nick Piggin <nickpiggin@...oo.com.au>
>     Signed-off-by: Ingo Molnar <mingo@...e.hu>
> 
> :040000 040000 029e79e0a7421438c2a7437dd210a1acf40b6c29 b581716762c1952c0f515fac642690514e7224b7 M      include
> :040000 040000 5f604b60974dbb9b0ac1a0910234f28c43a5e691 10c576cabe7eae661501ec38861a0f7488d5353b M      kernel

However does a futex change make ext3 crap its pants?

Is there anything more to it than start the machine, and reboot?

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html