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: <20200807200724.GZ7657@mit.edu> Date: Fri, 7 Aug 2020 16:07:24 -0400 From: tytso@....edu To: Jan Kara <jack@...e.cz> Cc: <linux-ext4@...r.kernel.org>, stable@...r.kernel.org Subject: Re: [PATCH] ext4: Fix checking of entry validity Thanks, applied, although I changed the commit summary to be: ext4: fix checking of directory entry validity for inline directories - Ted On Fri, Jul 31, 2020 at 06:21:35PM +0200, Jan Kara wrote: > ext4_search_dir() and ext4_generic_delete_entry() can be called both for > standard director blocks and for inline directories stored inside inode > or inline xattr space. For the second case we didn't call > ext4_check_dir_entry() with proper constraints that could result in > accepting corrupted directory entry as well as false positive filesystem > errors like: > > EXT4-fs error (device dm-0): ext4_search_dir:1395: inode #28320400: > block 113246792: comm dockerd: bad entry in directory: directory entry too > close to block end - offset=0, inode=28320403, rec_len=32, name_len=8, > size=4096 > > Fix the arguments passed to ext4_check_dir_entry(). > > Fixes: 109ba779d6cc ("ext4: check for directory entries too close to block end") > CC: stable@...r.kernel.org > Signed-off-by: Jan Kara <jack@...e.cz> > --- > fs/ext4/namei.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-)
Powered by blists - more mailing lists