linux-ext4 - Re: [PATCH] [RESEND] ext3: set i_extra

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]

Date:	Wed, 25 Aug 2010 20:36:57 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Andreas Dilger <adilger@...ger.ca>
Cc:	Jan Kara <jack@...e.cz>,
	Masayoshi MIZUMA <m.mizuma@...fujitsu.com>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] [RESEND] ext3: set i_extra_isize of 11th inode

On Wed, Aug 25, 2010 at 05:39:11PM -0600, Andreas Dilger wrote:
> 
> The fix to e2fsck for this issue has been around for a long time,
> AFAIK.  It was only needed in the kernel while the broken mke2fs was
> in wide use, and before a fixed e2fsck was available.

The mke2fs in question was fixed in e2fsprogs 1.37, over five years
ago.  Mizuma-san, why are you using such an __ancient__ mke2fs?  It
would seem that instead of fixing the kernel, the better thing to do
is to fix your version of e2fsprogs.  There have been enough other bug
fixes to e2fsck that using such an ancient version of e2fsck, if you
are willing to update the kernel, seems to not make a whole lot of
sense.

I certainly don't see the point of fixing making any changes in ext4
to accomodate such a change, since e2fsprogs which is that old won't
support ext4 file system features anyway.

							- 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