<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/f2fs/checkpoint.c, branch linux-3.17.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.17.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.17.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2014-08-22T20:56:47Z</updated>
<entry>
<title>f2fs: use macro for code readability</title>
<updated>2014-08-22T20:56:47Z</updated>
<author>
<name>Chao Yu</name>
</author>
<published>2014-08-22T08:17:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b5b822050ca3c4fc1f475100cc197cc00ba2d492'/>
<id>urn:sha1:b5b822050ca3c4fc1f475100cc197cc00ba2d492</id>
<content type='text'>
This patch introduces DEF_NIDS_PER_INODE/GET_ORPHAN_BLOCKS/F2FS_CP_PACKS macro
instead of numbers in code for readability.

change log from v1:
 o fix typo pointed out by Jaegeuk Kim.

Signed-off-by: Chao Yu &lt;chao2.yu@samsung.com&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: handle EIO not to break fs consistency</title>
<updated>2014-08-21T20:55:05Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2014-08-12T01:37:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cf779cab14d50a84b61399f758da269654b863db'/>
<id>urn:sha1:cf779cab14d50a84b61399f758da269654b863db</id>
<content type='text'>
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 &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: check s_dirty under cp_mutex</title>
<updated>2014-08-21T16:21:02Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2014-08-12T01:37:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8501017e50fb7586ba522a2913ce664d6c2024f6'/>
<id>urn:sha1:8501017e50fb7586ba522a2913ce664d6c2024f6</id>
<content type='text'>
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 &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: introduce f2fs_cp_error for readability</title>
<updated>2014-08-21T16:21:00Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2014-08-11T23:49:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1e968fdfe69e4060f05fa04059ecad93a0284e32'/>
<id>urn:sha1:1e968fdfe69e4060f05fa04059ecad93a0284e32</id>
<content type='text'>
This patch adds f2fs_cp_error for readability.

Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: trigger release_dirty_inode in f2fs_put_super</title>
<updated>2014-08-21T16:20:29Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2014-08-19T16:48:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6f12ac25f0167adb5d9ad5547fd6838380261e5c'/>
<id>urn:sha1:6f12ac25f0167adb5d9ad5547fd6838380261e5c</id>
<content type='text'>
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 &lt;chao2.yu@samsung.com&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: fix typo</title>
<updated>2014-08-19T17:01:33Z</updated>
<author>
<name>arter97</name>
</author>
<published>2014-08-06T14:22:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e1c42045203071c4634b89e696037357810d3083'/>
<id>urn:sha1:e1c42045203071c4634b89e696037357810d3083</id>
<content type='text'>
Fix typo and some grammatical errors.

The words "filesystem" and "readahead" are being used without the space treewide.

Signed-off-by: Park Ju Hyung &lt;qkrwngud825@gmail.com&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: reduce competition among node page writes</title>
<updated>2014-07-31T06:28:37Z</updated>
<author>
<name>Chao Yu</name>
</author>
<published>2014-07-03T10:58:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b3582c68920105e29d219714d8a6fbde25a43379'/>
<id>urn:sha1:b3582c68920105e29d219714d8a6fbde25a43379</id>
<content type='text'>
We do not need to block on -&gt;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 -&gt;node_write to
promote performance.

Signed-off-by: Chao Yu &lt;chao2.yu@samsung.com&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: avoid retrying wrong recovery routine when error was occurred</title>
<updated>2014-07-30T21:13:35Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2014-07-25T22:47:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cf2271e781cb16e1ca22be920010c2b64d90c338'/>
<id>urn:sha1:cf2271e781cb16e1ca22be920010c2b64d90c338</id>
<content type='text'>
This patch eliminates the propagation of recovery errors to the next mount.

Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: fix wrong condition for unlikely</title>
<updated>2014-07-30T21:13:31Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2014-07-25T14:41:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=01229f5e1b21b378863c91f8c653bbd8e593858c'/>
<id>urn:sha1:01229f5e1b21b378863c91f8c653bbd8e593858c</id>
<content type='text'>
This patch fixes the wrongly used unlikely condition.

Reviewed-by: Chao Yu &lt;chao2.yu@samsung.com&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: add info of appended or updated data writes</title>
<updated>2014-07-29T14:46:11Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2014-07-25T14:40:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fff04f90c1b9f91b9c513a89702a4b9ffe5dc1c5'/>
<id>urn:sha1:fff04f90c1b9f91b9c513a89702a4b9ffe5dc1c5</id>
<content type='text'>
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 &lt;chao2.yu@samsung.com&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
</feed>
