linux-kernel - Re: BUG: using rootfstype=ext4 causes oops

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: <20090416041945.GK21586@mit.edu>
Date:	Thu, 16 Apr 2009 00:19:45 -0400
From:	Theodore Tso <tytso@....edu>
To:	Andrew Price <andy@...rewprice.me.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: BUG: using rootfstype=ext4 causes oops

On Wed, Apr 15, 2009 at 09:59:26PM +0100, Andrew Price wrote:
> Using rootfstype=ext4 with today's linux-2.6.git causes a panic on my
> two amd64 machines (haven't tested it on any others). 

Hmm, git commit id, please?  The stack traces are in the IDE interrupt
handler, so it seems surprising that ext4 would trigger it but ext3
would not.  Have you tried ext4 on any earlier kernel?

The main difference I can think of is that ext4 enables barriers by
default; maybe that's the case of the IDE breakage?  Can you try
booting with the boot command option "rootfsflags=barrier=0" as well
as "rootfstype=ext4", and see if that helps?

If so, it's a bug in the IDE code in that it's not handling barriers
correctly.

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