| 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
| ||
|
Message-ID: <20130909145341.GI6059@thunk.org> Date: Mon, 9 Sep 2013 10:53:41 -0400 From: Theodore Ts'o <tytso@....edu> To: Eric Whitney <enwlinux@...il.com> Cc: linux-ext4@...r.kernel.org Subject: Re: [PATCH v2] Don't report uninit extents past EOF invalid On Wed, Aug 14, 2013 at 02:30:07PM -0400, Eric Whitney wrote: > Commit d3f32c2db8 introduced a regression that caused e2fsck failures > in xfstests generic 013, 070, 083, 091, and 263. Uninitialized > extents created by fallocate() at the end of file with the > FALLOC_FL_KEEP_SIZE flag were identified as invalid. However, > because the file size is not increased when FALLOC_FL_KEEP_SIZE is > used, uninitialized extents can correctly contain blocks located past > the end of file. > > Fix this by filtering out possible invalid extents if they are > uninitialized and extend past the block containing the end of file. > > Signed-off-by: Eric Whitney <enwlinux@...il.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
Powered by blists - more mailing lists