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: <20090114044059.GA6222@mit.edu>
Date:	Tue, 13 Jan 2009 23:40:59 -0500
From:	Theodore Tso <tytso@....edu>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: kernel BUG at fs/ext/super.c:428

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....

						- Ted
--
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