summaryrefslogtreecommitdiffstats
path: root/fs/ext4/xattr.c
diff options
context:
space:
mode:
authorzhangyi (F) <yi.zhang@huawei.com>2021-03-03 21:17:02 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-03-24 11:07:38 +0100
commit5cdacb4181694713d849f80890bc8cb66143d99d (patch)
treefd841fb8c60df1a31685fd0c6c34f51613f723c7 /fs/ext4/xattr.c
parent1454a47fb97adcf17535316481f70d43c8e4f500 (diff)
downloadlinux-stable-5cdacb4181694713d849f80890bc8cb66143d99d.tar.gz
linux-stable-5cdacb4181694713d849f80890bc8cb66143d99d.tar.bz2
linux-stable-5cdacb4181694713d849f80890bc8cb66143d99d.zip
ext4: find old entry again if failed to rename whiteout
commit b7ff91fd030dc9d72ed91b1aab36e445a003af4f upstream. If we failed to add new entry on rename whiteout, we cannot reset the old->de entry directly, because the old->de could have moved from under us during make indexed dir. So find the old entry again before reset is needed, otherwise it may corrupt the filesystem as below. /dev/sda: Entry '00000001' in ??? (12) has deleted/unused inode 15. CLEARED. /dev/sda: Unattached inode 75 /dev/sda: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Fixes: 6b4b8e6b4ad ("ext4: fix bug for rename with RENAME_WHITEOUT") Cc: stable@vger.kernel.org Signed-off-by: zhangyi (F) <yi.zhang@huawei.com> Link: https://lore.kernel.org/r/20210303131703.330415-1-yi.zhang@huawei.com Signed-off-by: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/ext4/xattr.c')
0 files changed, 0 insertions, 0 deletions