diff options
| author | Chao Yu <yuchao0@huawei.com> | 2020-03-19 19:57:58 +0800 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2020-03-30 20:46:24 -0700 |
| commit | 7bcd0cfa735d72037c71979f18a257b0c6a2b87f (patch) | |
| tree | ed313a1908e07492a352980a1f60a27cd6cb3c0a /security/tomoyo | |
| parent | 62f63eea291b50a5677ae7503ac128803174698a (diff) | |
f2fs: don't trigger data flush in foreground operation
Data flush can generate heavy IO and cause long latency during
flush, so it's not appropriate to trigger it in foreground
operation.
And also, we may face below potential deadlock during data flush:
- f2fs_write_multi_pages
- f2fs_write_raw_pages
- f2fs_write_single_data_page
- f2fs_balance_fs
- f2fs_balance_fs_bg
- f2fs_sync_dirty_inodes
- filemap_fdatawrite -- stuck on flush same cluster
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'security/tomoyo')
0 files changed, 0 insertions, 0 deletions