wireguard-linux/fs/f2fs/gc.c, branch jd/unified-crypt-queue

f2fs: don't trigger data flush in foreground operation

2020-03-31T03:46:24Z

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 Signed-off-by: Jaegeuk Kim

f2fs: fix to update f2fs_super_block fields under sb_lock

2020-03-23T04:16:29Z

Fields in struct f2fs_super_block should be updated under coverage of sb_lock, fix to adjust update_sb_metadata() for that rule. Fixes: 04f0b2eaa3b3 ("f2fs: ioctl for removing a range from F2FS") Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: Fix mount failure due to SPO after a successful online resize FS

2020-03-23T04:16:28Z

Even though online resize is successfully done, a SPO immediately after resize, still causes below error in the next mount. [ 11.294650] F2FS-fs (sda8): Wrong user_block_count: 2233856 [ 11.300272] F2FS-fs (sda8): Failed to get valid F2FS checkpoint This is because after FS metadata is updated in update_fs_metadata() if the SBI_IS_DIRTY is not dirty, then CP will not be done to reflect the new user_block_count. Signed-off-by: Sahitya Tummala Reviewed-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: skip migration only when BG_GC is called

2020-03-19T18:41:26Z

FG_GC needs to move entire section more quickly. Reviewed-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: introduce DEFAULT_IO_TIMEOUT

2020-03-19T18:41:26Z

As Geert Uytterhoeven reported: for parameter HZ/50 in congestion_wait(BLK_RW_ASYNC, HZ/50); On some platforms, HZ can be less than 50, then unexpected 0 timeout jiffies will be set in congestion_wait(). This patch introduces a macro DEFAULT_IO_TIMEOUT to wrap a determinate value with msecs_to_jiffies(20) to instead HZ/50 to avoid such issue. Quoted from Geert Uytterhoeven: "A timeout of HZ means 1 second. HZ/50 means 20 ms, but has the risk of being zero, if HZ < 50. If you want to use a timeout of 20 ms, you best use msecs_to_jiffies(20), as that takes care of the special cases, and never returns 0." Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: skip GC when section is full

2020-03-19T18:41:26Z

This fixes skipping GC when segment is full in large section. Signed-off-by: Jaegeuk Kim

f2fs: add migration count iff migration happens

2020-03-19T18:41:26Z

If first segment is empty and migration_granularity is 1, we can't move this at all. Reviewed-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: clean up bggc mount option

2020-03-19T18:41:25Z

There are three status for background gc: on, off and sync, it's a little bit confused to use test_opt(BG_GC) and test_opt(FORCE_FG_GC) combinations to indicate status of background gc. So let's remove F2FS_MOUNT_BG_GC and F2FS_MOUNT_FORCE_FG_GC mount options, and add F2FS_OPTION().bggc_mode with below three status to clean up codes and enhance bggc mode's scalability. enum { BGGC_MODE_ON, /* background gc is on */ BGGC_MODE_OFF, /* background gc is off */ BGGC_MODE_SYNC, /* * background gc is on, migrating blocks * like foreground gc */ }; Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: clean up lfs/adaptive mount option

2020-03-19T18:41:25Z

This patch removes F2FS_MOUNT_ADAPTIVE and F2FS_MOUNT_LFS mount options, and add F2FS_OPTION.fs_mode with below two status to indicate filesystem mode. enum { FS_MODE_ADAPTIVE, /* use both lfs/ssr allocation */ FS_MODE_LFS, /* use lfs allocation only */ }; It can enhance code readability and fs mode's scalability. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: clean up codes with {f2fs_,}data_blkaddr()

2020-03-19T18:41:25Z

- rename datablock_addr() to data_blkaddr(). - wrap data_blkaddr() with f2fs_data_blkaddr() to clean up parameters. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim