kernel/git/stable/linux.git/fs/f2fs/node.c, branch linux-3.15.y

f2fs: check bdi->dirty_exceeded when trying to skip data writes

2014-07-17T23:23:19+00:00

commit 2743f865543c0c4a5e12fc13edb2bf89a6e9687c upstream. If we don't check the current backing device status, balance_dirty_pages can fall into infinite pausing routine. This can be occurred when a lot of directories make a small number of dirty dentry pages including files. Reported-by: Brian Chadwick Signed-off-by: Jaegeuk Kim Signed-off-by: Greg Kroah-Hartman

f2fs: adjust free mem size to flush dentry blocks

2014-07-17T23:23:19+00:00

commit 6fb03f3a40805a412c9b285010ffdc2e7563f81b upstream. If so many dirty dentry blocks are cached, not reached to the flush condition, we should fall into livelock in balance_dirty_pages. So, let's consider the mem size for the condition. Signed-off-by: Jaegeuk Kim Signed-off-by: Greg Kroah-Hartman

f2fs: use list_for_each_entry{_safe} for simplyfying code

2014-04-02T00:56:27+00:00

This patch use list_for_each_entry{_safe} instead of list_for_each{_safe} for simplfying code. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: avoid free slab cache under spinlock

2014-04-02T00:56:12+00:00

Move kmem_cache_free out of spinlock protection region for better performance. Change log from v1: o remove spinlock protection for kmem_cache_free in destroy_node_manager suggested by Jaegeuk Kim. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: return -EIO when node id is not matched

2014-04-01T08:38:26+00:00

During the cleaing of node segments, F2FS can get errored node blocks due to data race between node page lock and its valid bitmap operations. In that case, it needs to return an error to skip such the obsolete block copy. Signed-off-by: Jaegeuk Kim

f2fs: skip unnecessary node writes during fsync

2014-03-20T13:10:11+00:00

If multiple redundant fsync calls are triggered, we don't need to write its node pages with fsync mark continuously. So, this patch adds FI_NEED_FSYNC to track whether the latest node block is written with the fsync mark or not. If the mark was set, a new fsync doesn't need to write a node block. Otherwise, we should do a new node block with the mark for roll-forward recovery. Signed-off-by: Jaegeuk Kim

f2fs: remove unnecessary threshold

2014-03-20T13:10:09+00:00

The NM_WOUT_THRESHOLD is now obsolete since f2fs starts to control on a basis of the memory footprint. Signed-off-by: Jaegeuk Kim

f2fs: throttle the memory footprint with a sysfs entry

2014-03-20T13:10:09+00:00

This patch introduces ram_thresh, a sysfs entry, which controls the memory footprint used by the free nid list and the nat cache. Previously, the free nid list was controlled by MAX_FREE_NIDS, while the nat cache was managed by NM_WOUT_THRESHOLD. However, this approach cannot be applied dynamically according to the system. So, this patch adds ram_thresh that users can specify the threshold, which is in order of 1 / 1024. For example, if the total ram size is 4GB and the value is set to 10 by default, f2fs tries to control the number of free nids and nat caches not to consume over 10 * (4GB / 1024) = 10MB. Signed-off-by: Jaegeuk Kim

f2fs: avoid to drop nat entries due to the negative nr_shrink

2014-03-20T13:10:08+00:00

The try_to_free_nats should not receive the negative nr_shrink. Otherwise, it can drop all the nat entries by the while loop. Signed-off-by: Jaegeuk Kim

f2fs: call f2fs_wait_on_page_writeback instead of native function

2014-03-20T13:10:04+00:00

If a page is on writeback, f2fs can face with deadlock due to under writepages. This is caused by merging IOs inside f2fs, so if it comes to detect, let's throw merged IOs, which is implemented by f2fs_wait_on_page_writeback. Signed-off-by: Jaegeuk Kim