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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 16 Jun 2021 08:22:38 -0400 From: "Theodore Ts'o" <tytso@....edu> To: Jan Kara <jack@...e.cz> Cc: linux-ext4@...r.kernel.org, Eric Whitney <enwlinux@...il.com>, linux-fsdevel@...r.kernel.org, "Darrick J . Wong" <djwong@...nel.org> Subject: Re: [PATCH 3/3] ext4: Fix overflow in ext4_iomap_alloc() On Mon, Apr 12, 2021 at 12:23:33PM +0200, Jan Kara wrote: > A code in iomap alloc may overblock block number when converting it to > byte offset. Luckily this is mostly harmless as we will just use more > expensive method of writing using unwritten extents even though we are > writing beyond i_size. > > Fixes: 378f32bab371 ("ext4: introduce direct I/O write using iomap infrastructure") > Signed-off-by: Jan Kara <jack@...e.cz> This was part of the patch series "ext4: Fix data corruption when extending DIO write races with buffered read" but which fixes an unrelated problem. The patch series was dropped in favor of a different approach, but it looks like this patch is still applicable, so I've applied with a minor typo fix in the commit description. - Ted
Powered by blists - more mailing lists