kernel.git/fs/f2fs/file.c, branch linux-3.19.y

f2fs: cleanup path to need cp at fsync

2014-12-08T18:40:22Z

Added some commentaries for code readability and cleaned up if-statement clearly. Signed-off-by: Changman Lee Signed-off-by: Jaegeuk Kim

f2fs: check if inode state is dirty at fsync

2014-12-08T18:37:13Z

If inode state is dirty, go straight to write. Suggested-by: Jaegeuk Kim Signed-off-by: Changman Lee Signed-off-by: Jaegeuk Kim

f2fs: release inmemory pages when the file was closed

2014-12-08T18:35:15Z

If file is closed, let's drop inmemory pages. Signed-off-by: Jaegeuk Kim

f2fs: cleanup redundant macro

2014-12-01T22:16:50Z

We've already made fi and sbi for inode. Let's avoid duplicated work. Signed-off-by: Changman Lee Signed-off-by: Jaegeuk Kim

f2fs: convert inline_data when i_size becomes large

2014-11-11T22:16:12Z

If i_size becomes large outside of MAX_INLINE_DATA, we shoud convert the inode. Otherwise, we can make some dirty pages during the truncation, and those pages will be written through f2fs_write_data_page. At that moment, the inode has still inline_data, so that it tries to write non- zero pages into inline_data area. Signed-off-by: Jaegeuk Kim

f2fs: fix deadlock to grab 0'th data page

2014-11-11T22:15:48Z

The scenario is like this. One trhead triggers: f2fs_write_data_pages lock_page f2fs_write_data_page f2fs_lock_op <- wait The other thread triggers: f2fs_truncate truncate_blocks f2fs_lock_op truncate_partial_data_page lock_page <- wait for locking the page This patch resolves this bug by relocating truncate_partial_data_page. This function is just to truncate user data page and not related to FS consistency as well. And, we don't need to call truncate_inline_data. Rather than that, f2fs_write_data_page will finally update inline_data later. Signed-off-by: Jaegeuk Kim

f2fs: disable roll-forward when active_logs = 2

2014-11-06T04:05:53Z

The roll-forward mechanism should be activated when the number of active logs is not 2. Signed-off-by: Jaegeuk Kim

f2fs: introduce -o fastboot for reducing booting time only

2014-11-05T01:34:15Z

If a system wants to reduce the booting time as a top priority, now we can use a mount option, -o fastboot. With this option, f2fs conducts a little bit slow write_checkpoint, but it can avoid the node page reads during the next mount time. Signed-off-by: Jaegeuk Kim

f2fs: revisit inline_data to avoid data races and potential bugs

2014-11-05T01:34:11Z

This patch simplifies the inline_data usage with the following rule. 1. inline_data is set during the file creation. 2. If new data is requested to be written ranges out of inline_data, f2fs converts that inode permanently. 3. There is no cases which converts non-inline_data inode to inline_data. 4. The inline_data flag should be changed under inode page lock. Signed-off-by: Jaegeuk Kim

f2fs: should not truncate any inline_dentry

2014-11-04T00:07:34Z

If the inode has inline_dentry, we should not truncate any block indices. Signed-off-by: Jaegeuk Kim