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] [day] [month] [year] [list]

Message-ID: <1420846715.9731.1.camel@sipsolutions.net>
Date:	Sat, 10 Jan 2015 00:38:35 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Theodore Ts'o <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: ext4 wrote extents on ext2 fs?

On Fri, 2015-01-09 at 18:30 -0500, Theodore Ts'o wrote:

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

Ok, makes sense. It's a USB flash drive, so perhaps it just messed up
with its FTL and showed a deleted block in place of the real one.

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

Thanks for the confirmation.

Thanks,
johannes

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