kernel.git/fs/f2fs/super.c, branch linux-3.17.y

f2fs: simplify by using a literal

2014-08-28T16:25:29Z

We can make the code a bit simpler because we know that "!retry" is zero. Signed-off-by: Dan Carpenter Signed-off-by: Jaegeuk Kim

f2fs: fix incorrect calculation with total/free inode num

2014-08-21T20:57:06Z

Theoretically, our total inodes number is the same as total node number, but there are three node ids are reserved in f2fs, they are 0, 1 (node nid), and 2 (meta nid), and they should never be used by user, so our total/free inode number calculated in ->statfs is wrong. This patch indroduces F2FS_RESERVED_NODE_NUM and then fixes this issue by recalculating total/free inode number with the macro. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: handle EIO not to break fs consistency

2014-08-21T20:55:05Z

There are two rules when EIO is occurred. 1. don't write any checkpoint data to preserve the previous checkpoint 2. don't lose the cached dentry/node/meta pages So, at first, this patch adds set_page_dirty in f2fs_write_end_io's failure. Then, writing checkpoint/dentry/node blocks is not allowed. Note that, for the data pages, we can't just throw away by redirtying them. Otherwise, kworker can fall into infinite loop to flush them. (Ref. xfstests/019) Signed-off-by: Jaegeuk Kim

f2fs: check s_dirty under cp_mutex

2014-08-21T16:21:02Z

It needs to check s_dirty under cp_mutex, since s_dirty is reset under that mutex. And previous condition was not correct, since we can omit doing checkpoint when checkpoint was done followed by all the node pages were written back. Signed-off-by: Jaegeuk Kim

f2fs: introduce f2fs_cp_error for readability

2014-08-21T16:21:00Z

This patch adds f2fs_cp_error for readability. Signed-off-by: Jaegeuk Kim

f2fs: give a chance to mount again when encountering errors

2014-08-21T16:21:00Z

This patch gives another chance to try mount process when we encounter an error. This makes an effect on the roll-forward recovery failures as well. Signed-off-by: Jaegeuk Kim

f2fs: trigger release_dirty_inode in f2fs_put_super

2014-08-21T16:20:29Z

The generic_shutdown_super calls sync_filesystem, evict_inode, and then f2fs_put_super. In f2fs_evict_inode, we remain some dirty inode information so we should release them at f2fs_put_super. Reviewed-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: don't skip checkpoint if there is no dirty node pages

2014-08-19T17:01:35Z

This is the errorneous scenario. 1. write data 2. do checkpoint 3. produce some dirty node pages by the gc thread 4. write back dirty node pages 5. f2fs_put_super will skip the checkpoint, since dirty count for node pages is zero. This patch removes such the wrong condition check. Signed-off-by: Jaegeuk Kim

f2fs: fix typo

2014-08-19T17:01:33Z

Fix typo and some grammatical errors. The words "filesystem" and "readahead" are being used without the space treewide. Signed-off-by: Park Ju Hyung Signed-off-by: Jaegeuk Kim

f2fs: reduce competition among node page writes

2014-07-31T06:28:37Z

We do not need to block on ->node_write among different node page writers e.g. fsync/flush, unless we have a node page writer from write_checkpoint. So it's better use rw_semaphore instead of mutex type for ->node_write to promote performance. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim