linux-ext4 - Re: [PATCH 22/54] libext2fs: ext2fs_new_block2() should call alloc

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150329030842.GC19097@thunk.org>
Date:	Sat, 28 Mar 2015 23:08:42 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	"Darrick J. Wong" <darrick.wong@...cle.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 22/54] libext2fs: ext2fs_new_block2() should call
 alloc_block hook

On Mon, Jan 26, 2015 at 11:37:57PM -0800, Darrick J. Wong wrote:
> If ext2fs_new_block2() is called without a specific block map, we
> should call the alloc_block hook before checking fs->block_map.  This
> helps us to avoid a bug in e2fsck where we need to allocate a block
> but instead of consulting block_found_map, we use the FS bitmaps,
> which (prior to pass 5) could be wrong.
> 
> 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