linux-ext4 - Re: ext4 wrote extents on ext2 fs?

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: <20150109233009.GB31554@thunk.org>
Date:	Fri, 9 Jan 2015 18:30:09 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: ext4 wrote extents on ext2 fs?

On Fri, Jan 09, 2015 at 11:18:28PM +0100, Johannes Berg wrote:
> Hi,
> 
> I'm running - on an oldish kernel 3.14.26 - an ext2 filesystem with the
> ext4 module, on a 1GB USB pendrive. Today the system failed to come up
> properly (it's a small router providing my internet connectivity) and
> this is what e2fsck had to say about the filesystem:
> 
> # e2fsck /dev/sdb1 
> e2fsck 1.42.12 (29-Aug-2014)
> extroot contains a file system with errors, check forced.
> Pass 1: Checking inodes, blocks, and sizes
> Inode 15817 has EXTENTS_FL flag set on filesystem without extents support.
> Clear<y>? yes
> Inode 15818 has EXTENTS_FL flag set on filesystem without extents support.
> Clear<y>? yes
> Inode 15819 has EXTENTS_FL flag set on filesystem without extents support.
> Clear<y>? yes
> Inode 15820 has EXTENTS_FL flag set on filesystem without extents support.
> Clear<y>? yes
> Inode 15821 has EXTENTS_FL flag set on filesystem without extents support.
> Clear<y>? yes
> Inode 15822 has EXTENTS_FL flag set on filesystem without extents support.
> Clear<y>? yes
> Inode 15823 has EXTENTS_FL flag set on filesystem without extents support.
> Clear<y>? yes
> Inode 15824 has EXTENTS_FL flag set on filesystem without extents support.
> Clear<y>? yes
> 
> As you can see, the inodes that somehow ended up with extents were
> deleted in the process of this - perhaps this shouldn't actually have
> been a problem for ext4 reading the filesystem? However, based on the
> symptoms of the device failure I reckon that the contents of those files
> was corrupted.

What I suspect happened is that some kind of garbage --- perhaps
simply a single 4k block of 0xFF's --- got written into the inode
table.  This would trigger this sort of complaint from e2fsck.

> Perhaps this is just a consequence of check ordering though - maybe if
> the inode flags get corrupted then the EXTENTS flag is just the first
> one that will be tested in the e2fsck code?

Yes, this is one of the first things that e2fsck 1.42.x would test
for.

						- 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