linux-ext4 - Re: [PATCH 49/47] libext2fs: don't report garbage inodes with really large inodes

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: <20141203031818.GO13618@thunk.org>
Date:	Tue, 2 Dec 2014 22:18:18 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	"Darrick J. Wong" <darrick.wong@...cle.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 49/47] libext2fs: don't report garbage inodes with really
 large inodes

On Wed, Nov 26, 2014 at 04:01:36PM -0800, Darrick J. Wong wrote:
> If the inode size is large enough that there are fewer than two inodes
> per block, don't report an inode checksum failure as a garbage inode
> during the scan because the "more than half are broken" criteria that
> we use to decide if a block of inodes is garbage doesn't really apply.
> 
> 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