diff options
| author | Chao Yu <yuchao0@huawei.com> | 2018-10-06 22:03:38 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-11-06 15:05:17 +0300 |
| commit | ce43554395a3cfdb17421a39d9c59f364a85ee47 (patch) | |
| tree | 0ce1b5b9cd4e974bcd8520d9b470c34866ad0eeb /drivers | |
| parent | b619de076f9c9a17cb454f5e54b9c13740125c07 (diff) | |
| download | linux-ce43554395a3cfdb17421a39d9c59f364a85ee47.tar.xz | |
f2fs: fix to recover inode->i_flags of inode block during POR
[ Upstream commit 0c093b590efb5c1ccdc835868dc2ae94bd2e14dc ]
Testcase to reproduce this bug:
1. mkfs.f2fs /dev/sdd
2. mount -t f2fs /dev/sdd /mnt/f2fs
3. touch /mnt/f2fs/file
4. sync
5. chattr +a /mnt/f2fs/file
6. xfs_io -a /mnt/f2fs/file -c "fsync"
7. godown /mnt/f2fs
8. umount /mnt/f2fs
9. mount -t f2fs /dev/sdd /mnt/f2fs
10. xfs_io /mnt/f2fs/file
There is no error when opening this file w/o O_APPEND, but actually,
we expect the correct result should be:
/mnt/f2fs/file: Operation not permitted
The root cause is, in recover_inode(), we recover inode->i_flags more
than F2FS_I(inode)->i_flags, so fix it.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions