<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/f2fs/super.c, branch linux-4.0.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.0.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.0.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2015-02-12T01:04:44Z</updated>
<entry>
<title>f2fs: introduce a batched trim</title>
<updated>2015-02-12T01:04:44Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-27T01:41:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bba681cbb231920a786cd7303462fb2632af6f36'/>
<id>urn:sha1:bba681cbb231920a786cd7303462fb2632af6f36</id>
<content type='text'>
This patch introduces a batched trimming feature, which submits split discard
commands.

This is to avoid long latency due to huge trim commands.
If fstrim was triggered ranging from 0 to the end of device, we should lock
all the checkpoint-related mutexes, resulting in very long latency.

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: should fail mount when trying to recover data on read-only dev</title>
<updated>2015-02-12T01:04:42Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-24T03:16:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=081d78c2fc4ab2fef4cdf1100dd22155c73f8657'/>
<id>urn:sha1:081d78c2fc4ab2fef4cdf1100dd22155c73f8657</id>
<content type='text'>
If device is read-only, we should not proceed data recovery.
But, if the previous checkpoint was done by normal clean shutdown, it's safe to
proceed the recovery, since there will be no data to be recovered.

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: split UMOUNT and FASTBOOT flags</title>
<updated>2015-02-12T01:04:41Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-29T19:45:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=119ee9144534141822462e3e8a5ccc8dc537f712'/>
<id>urn:sha1:119ee9144534141822462e3e8a5ccc8dc537f712</id>
<content type='text'>
This patch adds FASTBOOT flag into checkpoint as follows.

 - CP_UMOUNT_FLAG is set when system is umounted.
 - CP_FASTBOOT_FLAG is set when intermediate checkpoint having node summaries
   was done.

So, if you get CP_UMOUNT_FLAG from checkpoint, the system was umounted cleanly.
Instead, if there was sudden-power-off, you can get CP_FASTBOOT_FLAG or nothing.

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: support norecovery mount option</title>
<updated>2015-02-12T01:04:40Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-24T02:33:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2d834bf9ac8e40d9ae2a2dcde2348bd028f87ec4'/>
<id>urn:sha1:2d834bf9ac8e40d9ae2a2dcde2348bd028f87ec4</id>
<content type='text'>
This patch adds a mount option, norecovery, which is mostly same as
disable_roll_forward. The only difference is that norecovery should be activated
with read-only mount option.

This can be used when user wants to check whether f2fs is mountable or not
without any recovery process. (e.g., xfstests/200)

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 not to drop mount options when retrying fill_super</title>
<updated>2015-02-12T01:04:39Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-24T01:41:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dabc4a5c60f796a8e7171272284ba077f9c1e439'/>
<id>urn:sha1:dabc4a5c60f796a8e7171272284ba077f9c1e439</id>
<content type='text'>
If wrong mount option was requested, f2fs tries to fill_super again.
But, during the next trial, f2fs has no valid mount options, since
parse_options deleted all the separators in the original string.

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: merge flags in struct f2fs_sb_info</title>
<updated>2015-02-12T01:04:38Z</updated>
<author>
<name>Chao Yu</name>
</author>
<published>2015-01-28T09:48:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=caf0047e7e1e60a7ad1d655d3b81b32e2dfb6095'/>
<id>urn:sha1:caf0047e7e1e60a7ad1d655d3b81b32e2dfb6095</id>
<content type='text'>
Currently, there are several variables with Boolean type as below:

struct f2fs_sb_info {
...
	int s_dirty;
	bool need_fsck;
	bool s_closing;
...
	bool por_doing;
...
}

For this there are some issues:
1. there are some space of f2fs_sb_info is wasted due to aligning after Boolean
   type variables by compiler.
2. if we continuously add new flag into f2fs_sb_info, structure will be messed
   up.

So in this patch, we try to:
1. switch s_dirty to Boolean type variable since it has two status 0/1.
2. merge s_dirty/need_fsck/s_closing/por_doing variables into s_flag.
3. introduce an enum type which can indicate different states of sbi.
4. use new introduced universal interfaces is_sbi_flag_set/{set,clear}_sbi_flag
   to operate flags for sbi.

After that, above issues will be fixed.

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: do checkpoint when umount flag is not set</title>
<updated>2015-02-12T01:04:33Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-15T01:41:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=85dc2f2c6c84e99e9864ef660f79683aaad85f42'/>
<id>urn:sha1:85dc2f2c6c84e99e9864ef660f79683aaad85f42</id>
<content type='text'>
If the previous checkpoint was done without CP_UMOUNT flag, it needs to do
checkpoint with CP_UMOUNT for the next fast boot.

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: trigger correct checkpoint during umount</title>
<updated>2015-02-12T01:04:32Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-15T00:34:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=30a5537f9a9e91937aad6a47f55683f7ce0be257'/>
<id>urn:sha1:30a5537f9a9e91937aad6a47f55683f7ce0be257</id>
<content type='text'>
This patch fixes to trigger checkpoint with umount flag when kill_sb was called.
In kill_sb, f2fs_sync_fs was finally called, but at this time, f2fs can't do
checkpoint with CP_UMOUNT.
After then, f2fs_put_super is not doing checkpoint, since it is not dirty.

So, this patch adds a flag to indicate f2fs_sync_fs is called during umount.

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 f2fs_destroy_trace_ios to free radix tree</title>
<updated>2015-01-10T01:02:28Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-07T22:09:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=351f4fba843db3303a92897b21a3d4dff4b6c717'/>
<id>urn:sha1:351f4fba843db3303a92897b21a3d4dff4b6c717</id>
<content type='text'>
This patch removes radix tree after finishing tracing IOs.

Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: add spin_lock to cover radix operations in IO tracer</title>
<updated>2015-01-10T01:02:28Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2015-01-07T22:07:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c05086506f2204bcf02c9d3eb7950cdf0d8a3bef'/>
<id>urn:sha1:c05086506f2204bcf02c9d3eb7950cdf0d8a3bef</id>
<content type='text'>
This patch adds spin_lock to cover radix tree operations in IO tracer.

Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
</feed>
