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: <8B4A0D91-D3E1-4328-890C-BD66189598B5@dilger.ca>
Date:	Wed, 25 Aug 2010 17:39:11 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Jan Kara <jack@...e.cz>
Cc:	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 2010-08-25, at 17:04, Jan Kara wrote:
>> What size is the inode ? This problem happens if the size is larger than 128 byte. (I tested at 256 byte inode.)
> 
> Ah, that was the reason. Thanks. But looking at the implications, I'm a bit
> reluctant to do the change you propose. If someone has a filesystem created
> by old mkfs, he could suddently see corrupted xattrs in his lost+found
> directory with the new kernel. Not that there would be a big chance this
> happens but people run various strange environments...

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.


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