summaryrefslogtreecommitdiffstats
path: root/fs/fs_context.c
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2020-07-31 18:21:35 +0200
committerTheodore Ts'o <tytso@mit.edu>2020-08-07 22:04:27 +0200
commit7303cb5bfe845f7d43cd9b2dbd37dbb266efda9b (patch)
tree8b54df9eeccd55137323f950ca9bcbd681d4876a /fs/fs_context.c
parentfs: prevent BUG_ON in submit_bh_wbc() (diff)
downloadlinux-7303cb5bfe845f7d43cd9b2dbd37dbb266efda9b.tar.xz
linux-7303cb5bfe845f7d43cd9b2dbd37dbb266efda9b.zip
ext4: fix checking of directory entry validity for inline directories
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@vger.kernel.org Signed-off-by: Jan Kara <jack@suse.cz> Link: https://lore.kernel.org/r/20200731162135.8080-1-jack@suse.cz Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/fs_context.c')
0 files changed, 0 insertions, 0 deletions