ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
authorBaokun Li <libaokun1@huawei.com>
Wed, 26 Oct 2022 04:23:09 +0000 (12:23 +0800)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 9 Dec 2022 02:49:23 +0000 (21:49 -0500)
commit63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023
tree4ed38e687a8091cd17a1a9499802083fb2157dab
parent07342ec259df2a35d6a34aebce010567a80a0e15
ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode

There are many places that will get unhappy (and crash) when ext4_iget()
returns a bad inode. However, if iget the boot loader inode, allows a bad
inode to be returned, because the inode may not be initialized. This
mechanism can be used to bypass some checks and cause panic. To solve this
problem, we add a special iget flag EXT4_IGET_BAD. Only with this flag
we'd be returning bad inode from ext4_iget(), otherwise we always return
the error code if the inode is bad inode.(suggested by Jan Kara)

Signed-off-by: Baokun Li <libaokun1@huawei.com>
Reviewed-by: Jason Yan <yanaijie@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Link: https://lore.kernel.org/r/20221026042310.3839669-4-libaokun1@huawei.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
fs/ext4/ext4.h
fs/ext4/inode.c
fs/ext4/ioctl.c