linux.git/fs/f2fs/data.c, branch v3.17

f2fs: avoid double lock in truncate_blocks

2014-08-21T20:57:01+00:00

The init_inode_metadata calls truncate_blocks when error is occurred.
The callers holds f2fs_lock_op, so we should not call it again in
truncate_blocks.

Signed-off-by: Jaegeuk Kim

f2fs: handle EIO not to break fs consistency

2014-08-21T20:55:05+00:00

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: should convert inline_data during the mkwrite

2014-08-19T17:01:33+00:00

If mkwrite is called to an inode having inline_data, it can overwrite the data
index space as NEW_ADDR. (e.g., the first 4 bytes are coincidently zero)

Signed-off-by: Jaegeuk Kim

f2fs: fix typo

2014-08-19T17:01:33+00:00

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: add tracepoint for f2fs_direct_IO

2014-08-02T14:34:46+00:00

This patch adds a tracepoint for f2fs_direct_IO.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: add info of appended or updated data writes

2014-07-29T14:46:11+00:00

This patch introduces a inode number list in which represents inodes having
appended data writes or updated data writes after last checkpoint.
This will be used at fsync to determine whether the recovery information
should be written or not.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: add nobarrier mount option

2014-07-29T12:27:48+00:00

This patch adds a mount option, nobarrier, in f2fs.
The assumption in here is that file system keeps the IO ordering, but
doesn't care about cache flushes inside the storages.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: add f2fs_balance_fs for direct IO

2014-07-25T15:13:58+00:00

Otherwise, if a large amount of direct IO writes were done, the
segment allocation may be failed because no enough segments are gced.

Changes:

v2: add f2fs_balance_fs into __get_data_block instead of f2fs_direct_IO.

Signed-off-by: Huang, Ying 
Signed-off-by: Jaegeuk Kim

f2fs: introduce f2fs_write_failed to handle error case when write

2014-07-09T21:04:26+00:00

When we fail in ->write_begin()/->direct_IO(), our allocated node block in disk
and page cache are still kept, despite these may not be used again.

This patch introduce f2fs_write_failed() to handle the error case of these two
interfaces, it will truncate page cache and blocks of this file according to
i_size.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: avoid unneeded SetPageUptodate in f2fs_write_end

2014-07-09T21:04:24+00:00

We have already set page update in ->write_begin, so we should remove redundant
SetPageUptodate in ->write_end.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim