linux-ext4 - Re: metadata_csum + e4defrag seems to cause problems

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: <20130429155715.23219.qmail@science.horizon.com>
Date:	29 Apr 2013 11:57:15 -0400
From:	"George Spelvin" <linux@...izon.com>
To:	gnehzuil.liu@...il.com, linux@...izon.com
Cc:	linux-ext4@...r.kernel.org
Subject: Re: metadata_csum + e4defrag seems to cause problems

> Yes, metatdata_csum + e4defrag could corrupt ext4 file system.  We have
> found this bug and it has been fixed by this commit (2656497b, it is in
> dev branch of ext4 tree).  I am not sure whether you use dev branch.
> Could you please tell me your kernel version?  If you don't use dev
> branch, could you please try dev branch of ext4 tree?  Here is the git
> link:
>   https://git.kernel.org/cgit/linux/kernel/git/tytso/ext4.git/log/?h=dev

I was running 3.8-rc7 at the time of the corruption; I rebooted to -rc8
as part of the recovery.

Yes, I already have the ext4 repository cloned, but that was just
for pulling a particular fix Ted recommended a while ago.  I've been
reluctant to use a branch labelled "dev" more routinely without more
reassurance that it's believed to be "brave" rather than "stupid" to
use in something other than a dedicated test environment.

I'll try v3.9 + ext4/dev.  Thank you!

(Current head is 0d606e2c9fcc:
"ext4: fix type-widening bug in inode table readahead code")
--
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