linux-ext4 - Re: [PATCH v2 15/21] e2fsck: fix conflicting extents|inlinedata inode flags

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:	Sun, 10 Aug 2014 18:43:18 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	"Darrick J. Wong" <darrick.wong@...cle.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH v2 15/21] e2fsck: fix conflicting extents|inlinedata
 inode flags

On Fri, Aug 08, 2014 at 09:24:29AM -0700, Darrick J. Wong wrote:
> If we come across an inode with the inline data and extents inode flag
> set, try to figure out the correct flag settings from the contents of
> i_block and i_size.  If i_blocks looks like an extent tree head, we'll
> make it an extent inode; if it's small enough for inline data, set it
> to that.  This leaves the weird gray area where there's no extent
> tree but it's too big for the inode -- if /could/ be a block map,
> change it to that; otherwise, just clear the inode.
> 
> v2: Don't add unnecessary variables.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@...cle.com>

Applied, thanks.

						- 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