diff options
| author | Sahitya Tummala <stummala@codeaurora.org> | 2019-11-13 13:31:03 +0300 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2019-11-20 01:41:21 +0300 |
| commit | 677017d196ba2a4cfff13626b951cc9a206b8c7c (patch) | |
| tree | e892d3c5ea3e54572efc436cde028bccff138ee0 /lib/mpi/mpiutil.c | |
| parent | c45d6002ff7a322022560e9b19ad867b01fec77f (diff) | |
| download | linux-677017d196ba2a4cfff13626b951cc9a206b8c7c.tar.xz | |
f2fs: Fix deadlock in f2fs_gc() context during atomic files handling
The FS got stuck in the below stack when the storage is almost
full/dirty condition (when FG_GC is being done).
schedule_timeout
io_schedule_timeout
congestion_wait
f2fs_drop_inmem_pages_all
f2fs_gc
f2fs_balance_fs
__write_node_page
f2fs_fsync_node_pages
f2fs_do_sync_file
f2fs_ioctl
The root cause for this issue is there is a potential infinite loop
in f2fs_drop_inmem_pages_all() for the case where gc_failure is true
and when there an inode whose i_gc_failures[GC_FAILURE_ATOMIC] is
not set. Fix this by keeping track of the total atomic files
currently opened and using that to exit from this condition.
Fix-suggested-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'lib/mpi/mpiutil.c')
0 files changed, 0 insertions, 0 deletions