diff options
| author | Chao Yu <yuchao0@huawei.com> | 2019-02-23 02:48:27 +0100 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2019-03-13 02:59:18 +0100 |
| commit | ca597bddedd94906cd761d8be6a3ad21292725de (patch) | |
| tree | 974be67f675dd86dd3d598f46cdd46d222e30c2b /fs/inode.c | |
| parent | f2fs: give random value to i_generation (diff) | |
| download | linux-ca597bddedd94906cd761d8be6a3ad21292725de.tar.xz linux-ca597bddedd94906cd761d8be6a3ad21292725de.zip | |
f2fs: fix to dirty inode for i_mode recovery
As Seulbae Kim reported in bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=202637
We didn't recover permission field correctly after sudden power-cut,
the reason is in setattr we didn't add inode into global dirty list
once i_mode is changed, so latter checkpoint triggered by fsync will
not flush last i_mode into disk, result in this problem, fix it.
Reported-by: Seulbae Kim <seulbae@gatech.edu>
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/inode.c')
0 files changed, 0 insertions, 0 deletions