linux-ext4 - Re: OOPs in ext4

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: <20140521145315.GA8868@thunk.org>
Date:	Wed, 21 May 2014 10:53:15 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Lukáš Czerner <lczerner@...hat.com>
Cc:	Arturo Borrero Gonzalez <arturo.borrero.glez@...il.com>,
	linux-ext4@...r.kernel.org
Subject: Re: OOPs in ext4

On Wed, May 21, 2014 at 03:20:20PM +0200, Lukáš Czerner wrote:
> 
> yes there is definitely a bug in the error handling code because we
> really should not hit that BUG_ON() later.

The bug in the error handling code is fixed in commit 66a4cb187, which
will be in 3.15.  I should have split apart the bug fix from the
general cleanup, to make it easier to backport to older kernels.  At
the time, I didn't realize that the bug was getting hit so often.

> However I am curious how we got this state in the first place. Can
> you provide the logs before the first oops ? Are there any more
> warnings ?

Also, after the system rebooted, what messages if any did e2fsck
report?

Thanks,

					- 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