linux-ext4 - Re: [PATCH] e2fsck: zap extent-format inode with no extent header

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]

Date:	Mon, 30 Nov 2015 14:22:14 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	"Darrick J. Wong" <darrick.wong@...cle.com>
Cc:	Bo Branten <bosse@....umu.se>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] e2fsck: zap extent-format inode with no extent header

On Sat, Nov 28, 2015 at 01:51:32PM -0800, Darrick J. Wong wrote:
> The kernel requires all inodes with the extent flag set to have a
> valid extent tree header in i_block.  The ext2fs_extent_open2 prefers
> to initialize the header if i_block is zeroed, but e2fsck never writes
> the new header to disk.  Since the kernel won't create inodes with the
> flag and no header anyway, zap such files.
> 
> Reported-by: Bo Branten <bosse@....umu.se>
> Signed-off-by: Darrick J. Wong <darrick.wong@...cle.com>

Thanks, applied.

						- 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