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]

Message-Id: <68814CB7-75D6-4CCD-9E60-F4BA6A462BBC@dilger.ca>
Date:	Wed, 25 Aug 2010 19:51:50 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Ted Ts'o <tytso@....edu>
Cc:	Jan Kara <jack@...e.cz>,
	Masayoshi MIZUMA <m.mizuma@...fujitsu.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] [RESEND] ext3: set i_extra_isize of 11th inode

On 2010-08-25, at 19:21, Ted Ts'o wrote:
> On Wed, Aug 25, 2010 at 06:55:49PM -0600, Andreas Dilger wrote:
>> 
>> I think you are missing the point.  I don't think it matters which
>> mke2fs is in use.  The problem is that ext3_iget() has a workaround
>> for this 5-year-old mke2fs bug that is actively causing a loss of
>> xattr data if lost+found is reallocated.
> 
> Ah, OK.  But it's still the case that the right answer at this point
> is to make ext3 code conform to ext4, and drop the workaround
> altogether.

That's exactly what the patch is doing. :-)

Cheers, Andreas





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