f2fs: keep dirty inodes selectively for checkpoint
authorJaegeuk Kim <jaegeuk@kernel.org>
Fri, 14 Oct 2016 18:51:23 +0000 (11:51 -0700)
committerJaegeuk Kim <jaegeuk@kernel.org>
Wed, 23 Nov 2016 20:11:08 +0000 (12:11 -0800)
commit7c45729a4d6d1c90879e6c5c2df325c2f6db7191
tree25a2eba8a74807d3c05d023e34b983e5bb3b3871
parent664ba972df9b96942191db3068274cc1db899774
f2fs: keep dirty inodes selectively for checkpoint

This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.

The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount

In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.

Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/acl.c
fs/f2fs/dir.c
fs/f2fs/extent_cache.c
fs/f2fs/f2fs.h
fs/f2fs/file.c
fs/f2fs/inline.c
fs/f2fs/inode.c
fs/f2fs/namei.c
fs/f2fs/super.c
fs/f2fs/xattr.c