It only measures the read performance.
Signed-off-by: Jaegeuk Kim
---
tools/f2fs_io/f2fs_io.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/tools/f2fs_io/f2fs_io.c b/tools/f2fs_io/f2fs_io.c
index 2d64eda81706..2ed9cb4184b8 100644
--- a/tools/f2fs_io/f2fs_io.c
Signed-off-by: Jaegeuk Kim
---
tools/f2fs_io/f2fs_io.c | 32 ++--
1 file changed, 26 insertions(+), 6 deletions(-)
diff --git a/tools/f2fs_io/f2fs_io.c b/tools/f2fs_io/f2fs_io.c
index b9bf9bc5f797..2d64eda81706 100644
--- a/tools/f2fs_io/f2fs_io.c
+++ b/tools/f2fs_io
Signed-off-by: Jaegeuk Kim
---
tools/f2fs_io/f2fs_io.c | 4
1 file changed, 4 insertions(+)
diff --git a/tools/f2fs_io/f2fs_io.c b/tools/f2fs_io/f2fs_io.c
index 2ed9cb4184b8..248cf7a44a34 100644
--- a/tools/f2fs_io/f2fs_io.c
+++ b/tools/f2fs_io/f2fs_io.c
@@ -101,6 +101,10 @@ static void
Do we need this?
On 09/16, Chao Yu wrote:
> Add a sanity check in __update_extent_tree_range() to detect any
> zero-sized extent update.
>
> Signed-off-by: wangzijie
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/extent_cache.c | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --git a/fs/f2
On 09/17, wangzijie wrote:
> Script to reproduce:
> f2fs_io write 1 0 1881 rand dsync testfile
> f2fs_io fallocate 0 7708672 4096 testfile
> f2fs_io write 1 1881 1 rand buffered testfile
> fsync testfile
> umount
> mount
> f2fs_io precache_extents testfile
>
> When the data layout is something lik
at of memory.
>
> Therefore, I also agree that F2FS should first support uncached buffer
> IO for reads, as Chao mentioned.
Thanks, could you please post a patch and get some comments back?
>
> Thanks,
>
> On 2025/9/16 11:13, Chao Yu wrote:
> > On 9/12/25 07
Could you please share some trends of relation between has_enough_free_blocks()
vs. has_enough_dirty_blocks()? I'm wondering whethere there's a missing case
where has_enough_free_blocks() is not enough.
On 09/09, Liao Yuanhong wrote:
> Incorporate a check using has_enough_dirty_blocks() to prevent
On 09/15, wangzijie wrote:
> When we get wrong extent info data, and look up extent_node in rb tree,
> it will cause infinite loop (CONFIG_F2FS_CHECK_FS=n). Avoiding this by
> return NULL.
This is the exact buggy case which we should fix the original one. Have
you seen this error? In that case, ca
Given the performance data and implementation overhead, I'm also questioning
whether we really need to support this for writes or not. Can we get some common
sense of usage models?
On 08/28, Qi Han wrote:
> In the link [1], we adapted uncached buffer I/O read support in f2fs.
> Now, let's move for
This patch fixes to support different block size.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/sysfs.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/sysfs.c b/fs/f2fs/sysfs.c
index 081b5df0e664..7992386fb9e6 100644
--- a/fs/f2fs/sysfs.c
+++ b/fs/f2fs/sysfs.c
FUA writes can be merged to the existing write IOs.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 7961e0ddfca3..30cb2f230690 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -733,9
On 08/29, Jonathan Corbet wrote:
> Bagas Sanjaya writes:
>
> > Hi,
> >
> > Here are documentation formatting cleanup for f2fs. This also includes
> > docs retitle at the end of series ([6/6]) as a bonus.
> >
> > This series is based on docs-next tree.
> >
> > Enjoy!
> >
> > Bagas Sanjaya (6):
> >
On 08/30, Chao Yu wrote:
> On 8/30/2025 4:47 AM, Jaegeuk Kim wrote:
> > On 08/29, Chao Yu wrote:
> > > On 8/28/2025 11:23 PM, Jaegeuk Kim wrote:
> > > > On 08/28, Chao Yu wrote:
> > > > > On 8/28/25 05:52, Jaegeuk Kim via Linux-f2fs-devel wrote:
> &
On 08/29, Chao Yu wrote:
> On 8/28/2025 11:23 PM, Jaegeuk Kim wrote:
> > On 08/28, Chao Yu wrote:
> > > On 8/28/25 05:52, Jaegeuk Kim via Linux-f2fs-devel wrote:
> > > > Let's split IPU writes in hot data area to improve the GC efficiency.
> > >
> &
On 08/28, Chao Yu wrote:
> On 8/28/25 05:52, Jaegeuk Kim via Linux-f2fs-devel wrote:
> > Let's split IPU writes in hot data area to improve the GC efficiency.
>
> I didn't get it, IPU may be not friendly for migrating data along w/ write in
> hot area?
This de
Let's split IPU writes in hot data area to improve the GC efficiency.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index e0f6589c6a1c..bb79dad55ac9 100644
--- a/fs/f2fs/segm
On 08/20, Chao Yu wrote:
> On 8/6/25 20:32, mason.zhang wrote:
> > This fix combines the space check for data_blocks and dent_blocks when
> > verifying HOT_DATA segment capacity, preventing potential insufficient
> > space issues during checkpoint.
> >
> > Fixes: bf34c93d2645 ("f2fs: check curseg
1048576 1048576
Reviewed-by: Chao Yu
Signed-off-by: Jaegeuk Kim
---
v4:
- change the entry names clearly
fs/f2fs/sysfs.c | 64 +
1 file changed, 64 insertions(+)
diff --git a/fs/f2fs/sysfs.c b/fs/f2fs/sysfs.c
index 1ffaf9e74ce9
On 08/15, Liao Yuanhong wrote:
> Introduces two new sys nodes: device_border_line and device_alloc_policy.
> The device_border_line identifies the boundary between devices, measured
> in sections; it defaults to the end of the device for single storage
> setups, and the end of the first device for
Status Offset (kb)
Length (kb)Cached pages (kb)
---
/local/tmp/test2 Donated 0
1048576 2097152
/local/tmp/test Evicted 0
1048576
Status Offset (kb)
Length (kb)Cached pages (kb)
---
/local/tmp/test2 Donated 0
1048576 2097152
/local/tmp/test Evicted 0
1048576
Status Offset (kb)
Length (kb)Cached pages (kb)
---
/local/tmp/test2 Donated 0
1048576 2097152
/local/tmp/test Evicted 0
1048576
On 08/08, 王晓珺 wrote:
> 在 2025/8/8 12:16, Chao Yu 写道:
> > Xiaojun,
> >
> > I just notice generic/483 will fail w/ this change, can you please take a
> > look?
> >
> > Thanks,
>
> Hi Chao,
>
> OK, Thanks for pointing out the issue.
Yeah, I'm also hitting several failures in xfstests. Hence, I drop
By the way, can we also add some testcases in xfstests to check all this
works as intended?
On 08/07, Chunhai Guo wrote:
> This patch allows privileged users to reserve nodes via the
> 'reserve_node' mount option, which is similar to the existing
> 'reserve_root' option.
>
> "-o reserve_node=" me
Chao, it seems you made a clean up before this? Can you post it first?
On 08/04, Chao Yu wrote:
> generic/091 may fail, then it bisects to the bad commit ba8dac350faf
> ("f2fs: fix to zero post-eof page").
>
> What will cause generic/091 to fail is something like below Testcase #1:
> 1. write 16k
On 07/31, Chunhai Guo wrote:
> 在 7/31/2025 4:46 PM, Chao Yu 写道:
> > On 7/31/25 15:57, Chunhai Guo wrote:
> >> This patch allows privileged users to reserve nodes via the
> >> 'reserve_node' mount option, which is similar to the existing
> >> 'reserve_root' option.
> >>
> >> "-o reserve_node=" means
duce fs_context_operation structure
f2fs: switch to the new mount api
Jaegeuk Kim (2):
f2fs: check the generic conditions first
f2fs: drop inode from the donation list when the last file is closed
Jan Prusakowski (1):
f2fs: vm_unmap_ram() may be called from an invalid
~~~
404 | get_sb(segment0_blkaddr),
c.zone_blocks);
| ~~^~
external/f2fs-tools/include/f2fs_fs.h:289:18: note: expanded from macro 'MSG'
289 | pr
Let's drop the inode from the donation list when there is no other
open file.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 2 ++
fs/f2fs/file.c | 8 +++-
fs/f2fs/inode.c | 2 +-
fs/f2fs/super.c | 1 +
4 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/f2fs.h
On 07/29, Chao Yu wrote:
> generic/299 w/ mode=lfs will cause long time latency, let's dump more
> information once we hit case.
>
> CP merge:
> - Queued :0
> - Issued :1
> - Total :1
> - Cur time : 7565(ms)
> - Peak time : 7565(ms)
>
> F2FS-fs (vdc): checkpoint was blocked
Applied with limiting 80 columns.
On 05/16, Cherniaev Andrei wrote:
> I think my optimization makes mkfs.f2fs faster in case of invalid volume
> size. So with the commit user will get err faster.
> Before start I suggest add debug printf() to `f2fs_fs.h` like this:
> ```
> for (; candidate <= end
Please check
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/log/?h=dev-test
On 07/28, Daeho Jeong wrote:
> From: Daeho Jeong
>
> Add a sysfs knob to set a multiplier for the background GC migration
> window when F2FS Garbage Collection is boosted.
>
> Signed-off-by: Daeho Jeo
On 07/22, Chao Yu wrote:
> On 7/19/25 05:50, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > Add this to control GC algorithm for boost GC.
> >
> > Signed-off-by: Daeho Jeong
> > ---
> > v2: use GC_GREEDY instead of 1
> > ---
> > Documentation/ABI/testing/sysfs-fs-f2fs | 8 +++-
> > fs/f
I think this is a simple hack, so NAK.
It seems the ask is to support storage tiering, and we need to design a better
approach. Something like allocating a section per defined device priority.
On 07/23, Liao Yuanhong wrote:
> During the development process, we encounter the following two issues:
Can we disable linear lookup by default, but add an option to enable it?
On 07/24, Chao Yu wrote:
> It provides a way to disable linear lookup fallback during mkfs.
>
> Usage:
>
> 1. Disable linear lookup:
> mkfs.f2fs -f -O casefold -C utf8:hashonly /dev/vdb
> dump.f2fs -d3 /dev/vdb |grep s_enco
I think it'd be better to add a parameter like __lookup_nat_cache(for_dirty).
On 07/18, wangzijie wrote:
> __lookup_nat_cache follows LRU manner to move clean nat entry, when nat
> entries are going to be dirty, no need to move them to tail of lru list.
>
> Signed-off-by: wangzijie
> ---
> fs/f
On 07/14, Chao Yu wrote:
> Daniel,
>
> It missed to add doc entry, just found the issue.
Can you post another patch to update the doc?
>
> Thanks,
>
> On 6/17/25 22:04, Daniel Lee wrote:
> > A new command 'test_create_perf', has been introduced to measure
> > the performance of creating and de
On 07/14, Chao Yu wrote:
> - mkdir dir
> - f2fs_io test_lookup_perf -i /mnt/f2fs/dir 5
> - sync
> - echo 3 > /proc/sys/vm/drop_caches
> - f2fs_io test_lookup_perf /mnt/f2fs/dir
>
> Output:
> Measure readdir performance
> Measure stat performance
> Operation: total_files, total_time_s, throughp
On 07/10, Matthew Wilcox wrote:
> On Thu, Jul 10, 2025 at 02:26:38PM +0000, Jaegeuk Kim wrote:
> > On 07/10, Matthew Wilcox wrote:
> > > On Thu, Jul 10, 2025 at 03:17:28PM +0800, kernel test robot wrote:
> > > > >> fs/f2fs/data.c:58:56: erro
On 07/10, Matthew Wilcox wrote:
> On Thu, Jul 10, 2025 at 03:17:28PM +0800, kernel test robot wrote:
> > >> fs/f2fs/data.c:58:56: error: passing 'const struct folio *' to parameter
> > >> of type 'struct folio *' discards qualifiers
> > >> [-Werror,-Wincompatible-pointer-types-discards-qualifiers
Queued with this for testing.
--- a/fs/f2fs/recovery.c
+++ b/fs/f2fs/recovery.c
@@ -767,7 +767,7 @@ static int do_recover_data(struct f2fs_sb_info *sbi, struct
inode *inode,
out:
f2fs_notice(sbi, "recover_data: ino = %lx, nid = %x (i_size: %s), "
"range (%u, %u), reco
Hongbo,
Could you please post v5?
Thanks,
On 07/07, Hongbo Li wrote:
>
>
> On 2025/7/4 11:27, Chao Yu wrote:
> > On 6/2/25 17:02, Hongbo Li wrote:
> > > In handle_mount_opt, we use fs_parameter to parse each option.
> > > However we're still using the old API to get the options string.
> > > U
I think we can clean up more like this?
https://lore.kernel.org/linux-f2fs-devel/20250630160839.1142073-1-jaeg...@kernel.org/T/#u
On 06/30, wangzijie wrote:
> To prevent scattered pin block generation, don't allow non-section aligned
> truncation
> to smaller or equal size on pinned file. But fo
Let's return errors caught by the generic checks. This fixes generic/494 where
it expects to see EBUSY by setattr_prepare instead of EINVAL by f2fs for active
swapfile.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 24
1 file changed, 12 insertions(+), 12 dele
Hi Linus,
Could you please help mergint this bug fix series?
Thanks,
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.g
Hi,
Please do sbi conversion first, and apply this change.
On 06/18, wangzijie wrote:
> To prevent scattered pin block generation, don't allow non-section aligned
> truncation
> to smaller or equal size on pinned file. But for truncation to larger size,
> after
> commit 3fdd89b452c2("f2fs: prev
Hi Zhiguo,
This patch causes CPU hang when running fsstress on compressed/non-compressed
files. Please check.
On 06/05, Zhiguo Niu wrote:
> The decompress_io_ctx may be released asynchronously after
> I/O completion. If this file is deleted immediately after read,
> and the kworker of processing
Thanks you, Hongbo.
I just applied this series to the dev-test branch as below, and will
keep testing with incoming patches together. Let's see. :)
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/log/?h=dev-test
On 06/02, Hongbo Li wrote:
> In this version, we have finished the
es
f2fs: return bool from __write_node_folio
Colin Ian King (1):
f2fs: remove redundant assignment to variable err
Daeho Jeong (1):
f2fs: handle error cases of memory donation
Eric Biggers (1):
f2fs: remove unused sbi argument from checksum functions
Jaegeuk Kim (2):
Chao,
Can we add the similar path that other filesystems have?
On 05/21, Chao Yu wrote:
> fstest reports a f2fs bug:
>
> generic/363 42s ... [failed, exit status 1]- output mismatch (see
> /share/git/fstests/results//generic/363.out.bad)
> --- tests/generic/363.out 2025-01-12 21:57:40.271
Thanks, I added the patches back with this fix applied to the original patch. :)
On 05/28, Chao Yu wrote:
> syzbot report a f2fs bug as below:
>
> CPU: 0 UID: 0 PID: 5840 Comm: syz-executor138 Not tainted
> 6.15.0-rc7-next-20250523-syzkaller #0 PREEMPT(full)
> Call Trace:
>
> dump_stack_lvl+0x
On 05/16, Hongbo Li wrote:
>
>
> On 2025/5/14 23:30, Jaegeuk Kim wrote:
> > Hi, Hongbo,
> >
> > It seems we're getting more issues in the patch set. May I ask for some
> > help sending the new patch series having all the fixes that I made as well
> >
Hi, Hongbo,
It seems we're getting more issues in the patch set. May I ask for some
help sending the new patch series having all the fixes that I made as well
as addressing the concerns? You can get the patches from [1].
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/log/?h
On 05/13, Chao Yu wrote:
> mapping_read_folio_gfp() will return a folio, it should always be
> uptodate, let's check folio uptodate status to detect any potenial
> bug.
>
> Signed-off-by: Chao Yu
> ---
> v2:
> - just add f2fs_bug_on(), get rid of error handling.
> fs/f2fs/super.c | 6 ++
> 1
On 04/23, Eric Sandeen wrote:
> From: Hongbo Li
>
> The new mount api will execute .parse_param, .init_fs_context, .get_tree
> and will call .remount if remount happened. So we add the necessary
> functions for the fs_context_operations. If .init_fs_context is added,
> the old .mount should remov
On 05/13, Chao Yu wrote:
> On 5/13/25 10:19, Eric Sandeen wrote:
> > On 5/11/25 10:43 PM, Chao Yu wrote:
> >> On 5/8/25 23:59, Eric Sandeen wrote:
> >>> On 5/8/25 4:19 AM, Chao Yu wrote:
> > @@ -2645,21 +2603,11 @@ static int f2fs_remount(struct
> > super_block *sb, int *flags, char *data)
On 04/23, Eric Sandeen wrote:
> From: Hongbo Li
>
> The new mount api separates option parsing and super block setup
> into two distinct steps and so we need to separate the options
> parsing out of the parse_options().
>
> In order to achieve this, here we handle the mount options with
> three
On 05/12, Chao Yu wrote:
> mapping_read_folio_gfp() will return a folio, it should always be
> uptodate, let's check folio uptodate status to detect any potenial
> bug.
If it's supposed to be uptodate, can you add f2fs_bug_on() only?
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/super.c | 11
On 05/12, Chao Yu wrote:
> Add f2fs_bug_on() to check whether memory preallocation will fail or
> not after radix_tree_preload(GFP_NOFS | __GFP_NOFAIL).
Are we getting a bug?
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/checkpoint.c | 4 +++-
> fs/f2fs/node.c | 7 +--
> 2 files changed
On 05/07, Eric Sandeen wrote:
> On 5/7/25 2:48 PM, Jaegeuk Kim wrote:
> > On 05/07, Eric Sandeen wrote:
> >> On 5/7/25 9:46 AM, Jaegeuk Kim wrote:
> >>
> >>> I meant:
> >>>
> >>> # mkfs/mkfs.f2fs -c /dev/v...@vdc.file /dev/vdb
> &
On 05/07, Eric Sandeen wrote:
> On 5/7/25 3:28 PM, Jaegeuk Kim wrote:
> >> But as far as I can tell, at least for the extent cache, remount is handled
> >> properly already (with the hunk above):
> >>
> >> # mkfs/mkfs.f2fs -c /dev/v...@vdc.file /dev/vdb
&g
On 05/07, Eric Sandeen wrote:
> On 5/7/25 9:46 AM, Jaegeuk Kim wrote:
>
> > I meant:
> >
> > # mkfs/mkfs.f2fs -c /dev/v...@vdc.file /dev/vdb
> > # mount /dev/vdb mnt
> >
> > It's supposed to be successful, since extent_cache is enabled by default
On 05/07, Eric Sandeen wrote:
> On 5/7/25 6:26 AM, Chao Yu wrote:
> > On 4/20/25 23:25, Eric Sandeen wrote:
> >> From: Hongbo Li
> >>
> >> In handle_mount_opt, we use fs_parameter to parse each option.
> >> However we're still using the old API to get the options string.
> >> Using fsparams parse_
On 05/06, Eric Sandeen wrote:
> On 5/6/25 9:56 PM, Eric Sandeen wrote:
> > On 5/6/25 8:23 PM, Jaegeuk Kim wrote:
>
> ...
>
> >> What about:
> >> # mount -o loop,noextent_cache f2fsfile.img mnt
> >>
> >> In this case, 1) ctx_clear_opt(), 2)
On 05/06, Eric Sandeen wrote:
> On 5/6/25 7:35 PM, Jaegeuk Kim wrote:
> > Hmm, I had to drop the series at the moment, since it seems needing more
> > work to deal with default_options(), which breaks my device setup.
> > For example, set_opt(sbi, READ_EXTENT_CACHE) in d
Hmm, I had to drop the series at the moment, since it seems needing more
work to deal with default_options(), which breaks my device setup.
For example, set_opt(sbi, READ_EXTENT_CACHE) in default_options is not
propagating
to the below logics. In this case, do we need ctx_set_opt() if user doesn't
On 05/06, Eric Sandeen wrote:
> On 5/6/25 5:01 PM, Jaegeuk Kim wrote:
>
>
>
> >> +static int f2fs_check_opt_consistency(struct fs_context *fc,
> >> +struct super_block *sb)
> >> +{
> >> + struct f2fs_fs_context *c
On 04/23, Eric Sandeen wrote:
> From: Hongbo Li
>
> The new mount api separates option parsing and super block setup
> into two distinct steps and so we need to separate the options
> parsing out of the parse_options().
>
> In order to achieve this, here we handle the mount options with
> three
On 04/23, Eric Sandeen wrote:
> From: Hongbo Li
>
> In handle_mount_opt, we use fs_parameter to parse each option.
> However we're still using the old API to get the options string.
> Using fsparams parse_options allows us to remove many of the Opt_
> enums, so remove them.
>
> The checkpoint di
On 05/05, Eric Sandeen wrote:
> Hi all - it would be nice to get some review or feedback on this;
> seems that these patches tend to go stale fairly quickly as f2fs
> evolves. :)
Thank you so much for the work! Let me queue this series into dev-test for
tests. If I find any issue, let me ping to t
On 04/27, Chao Yu wrote:
> On 4/1/25 04:10, Matthew Wilcox (Oracle) wrote:
> > Support arbitrary size folios and remove a few hidden calls to
> > compound_head(). Also remove an unnecessary test of the uptodaate flag;
> > if mapping_read_folio_gfp() cannot bring the folio uptodate, it will
> > ret
On 04/28, Chao Yu wrote:
> On 4/1/25 04:10, Matthew Wilcox (Oracle) wrote:
> > Sorry for the length of this series. Each patch in this series builds,
> > but obviously I haven't done any testing. It should be easy to bisect
> > to any mistakes I've made. This conversion isn't complete; I estimat
If the device support write hints, let's assign it in Android devices.
Signed-off-by: Jaegeuk Kim
---
fsck/main.c | 4
mkfs/f2fs_format_main.c | 4
2 files changed, 8 insertions(+)
diff --git a/fsck/main.c b/fsck/main.c
index 423a9a63782c..cb51673aeda8 100644
--- a
Hi Matthew,
I had to apply this in this patch, since fio can be reassigned after
checking fio->in_list check.
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -946,7 +946,6 @@ static bool is_end_zone_blkaddr(struct f2fs_sb_info *sbi,
block_t blkaddr)
void f2fs_submit_page_write(struct f2fs_io_info
external/f2fs-tools/fsck/mount.c:584:4: error: 'snprintf' will always overflow;
destination buffer has size 30, but size argument is 31
[-Werror,-Wbuiltin-memcpy-chk-size]
584 | snprintf(str, 31, "%s[%d]", i == NAT_BITMAP ?
On 04/14, Chao Yu wrote:
> dump.f2fs -d 1 img
0206 R12: 7ffdc232eaf0
R13: 5d0cebb0 R14: 7ffdc232d958 R15: 0001
Cc: sta...@vger.kernel.org
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/namei.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
index 8f8b9b843bdf..f17cb24
On 04/07, Chao Yu wrote:
> On 4/7/25 10:08, Chao Yu wrote:
> > On 4/5/25 03:55, Jaegeuk Kim wrote:
> >> Hi Yohan,
> >>
> >> I modified this patch after applying the clean up by
> >>
> >> https://lore.kernel.org/linux-f2fs-devel/202504041954
On 03/19, Dan Carpenter wrote:
> On Wed, Mar 19, 2025 at 11:30:10AM +, Colin Ian King wrote:
> > The variable err is being assigned a value zero and then the following
> > goto page_hit reassigns err a new value. The zero assignment is redundant
> > and can be removed.
> >
> > Signed-off-by: C
Hi Yohan,
I modified this patch after applying the clean up by
https://lore.kernel.org/linux-f2fs-devel/20250404195442.413945-1-jaeg...@kernel.org/T/#u
--- a/fs/f2fs/segment.h
+++ b/fs/f2fs/segment.h
@@ -486,6 +486,11 @@ static inline void __set_test_and_free(struct f2fs_sb_info
*sbi,
No functional change.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.h | 40
1 file changed, 24 insertions(+), 16 deletions(-)
diff --git a/fs/f2fs/segment.h b/fs/f2fs/segment.h
index 0465dc00b349..5fcb1f92d506 100644
--- a/fs/f2fs/segment.h
+++ b/fs
Can we also update man page?
On 03/31, Chao Yu wrote:
> Support a new option --nolinear-lookup=X for fsck.f2fs to tune
> linear lookup fallback conditionally, X=1: disable linear lookup,
> X=0: enable linear lookup.
>
> This can help to 1) add a regression testcase to check kernel
> whether linea
It seems this patch breaks the multi-partition cases.
On 03/25, Chao Yu wrote:
> A zoned device can has both conventional zones and sequential zones,
> so we should not treat first segment of zoned device as first_zoned_segno,
> instead, we need to check zone type for each zone during traversing z
On 03/26, Matthew Wilcox wrote:
> On Fri, Mar 14, 2025 at 09:38:15PM +0000, Jaegeuk Kim wrote:
> > On 03/14, Matthew Wilcox wrote:
> > > Unfortunately, I thnk I have to abandon this effort. It's only going
> > > to make supporting large folios harder (ie ther
ather than sb to quota qf_name helpers
f2fs: pass sbi rather than sb to parse_options()
Jaegeuk Kim (6):
f2fs: introduce f2fs_base_attr for global sysfs entries
f2fs: add ioctl to get IO priority hint
f2fs: keep POSIX_FADV_NOREUSE ranges
f2fs: add a sysfs entry to re
Do we still need this patch?
On 03/21, Daeho Jeong wrote:
> From: Daeho Jeong
>
> support a file truncation to zero size for device aliasing files.
>
> Signed-off-by: Daeho Jeong
> ---
> v2: make the extent length zero
> ---
> fs/f2fs/file.c | 7 ++-
> 1 file changed, 6 insertions(+), 1 d
Ping.
On 03/17, Jaegeuk Kim via Linux-f2fs-devel wrote:
> This adds a fragread command in f2fs_io, which is able to measure the
> read performance on fragmented data buffer.
>
> Signed-off-by: Jaegeuk Kim
> ---
>
> Change log from v1:
> - add mlock
>
>
This adds a fragread command in f2fs_io, which is able to measure the
read performance on fragmented data buffer.
Signed-off-by: Jaegeuk Kim
---
tools/f2fs_io/f2fs_io.c | 114
1 file changed, 114 insertions(+)
diff --git a/tools/f2fs_io/f2fs_io.c b
This adds a fragread command in f2fs_io, which is able to measure the
read performance on fragmented data buffer.
Signed-off-by: Jaegeuk Kim
---
Change log from v1:
- add mlock
tools/f2fs_io/f2fs_io.c | 114
1 file changed, 114 insertions(+)
diff
On 03/12, Chunhai Guo wrote:
> fstrim may miss candidates that need to be discarded, as shown in the
> examples below.
>
> The root cause is that when cpc->reason is set with CP_DISCARD,
> add_discard_addrs() expects that ckpt_valid_map and cur_valid_map have
> been synced by seg_info_to_raw_sit()
On 03/14, Jaegeuk Kim wrote:
> On 03/14, Yeongjin Gil wrote:
> > In the case of the following call stack for an atomic file,
> > FI_DIRTY_INODE is set, but FI_ATOMIC_DIRTIED is not subsequently set.
> >
> > f2fs_file_write_iter
> > f2fs_map_block
On 03/14, Matthew Wilcox wrote:
> On Wed, Mar 12, 2025 at 01:22:41AM +0000, Jaegeuk Kim wrote:
> > On 03/12, Matthew Wilcox wrote:
> > > On Tue, Mar 11, 2025 at 07:50:38PM +, patchwork-bot+f...@kernel.org
> > > wrote:
> > > > Hello:
> > > >
On 03/14, Yeongjin Gil wrote:
> In the case of the following call stack for an atomic file,
> FI_DIRTY_INODE is set, but FI_ATOMIC_DIRTIED is not subsequently set.
>
> f2fs_file_write_iter
> f2fs_map_blocks
> f2fs_reserve_new_blocks
> inc_valid_block_count
> __mark_inode_dirty(
On 03/12, Matthew Wilcox wrote:
> On Tue, Mar 11, 2025 at 07:50:38PM +, patchwork-bot+f...@kernel.org wrote:
> > Hello:
> >
> > This series was applied to jaegeuk/f2fs.git (dev)
> > by Jaegeuk Kim :
>
> Thanks!
>
> FWIW, I have a tree with 75 pa
On 03/06, Chao Yu wrote:
> On 3/5/25 22:33, Jaegeuk Kim wrote:
> > Chao,
> >
> > How about disabling nat_bits during mount and removing all the relevant
> > codes
> > together?
>
> Jaegeuk, let me do this in separated patches:
> - remove recovery code
&
On 03/11, Chao Yu wrote:
> On 3/4/25 09:10, Jaegeuk Kim via Linux-f2fs-devel wrote:
> > From: Jaegeuk Kim
> >
> > This adds a fragread command in f2fs_io, which is able to measure the
> > read performance on fragmented data buffer.
> >
> > Signed-off-by:
On 03/07, Matthew Wilcox wrote:
> On Fri, Mar 07, 2025 at 08:39:56PM +0000, Jaegeuk Kim wrote:
> > On 03/07, Matthew Wilcox (Oracle) wrote:
> > > I was planning on sending this next cycle, but maybe there's time to
> > > squeeze these patches into the upcoming
Signed-off-by: Jaegeuk Kim
---
tools/f2fs_io/f2fs_io.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/f2fs_io/f2fs_io.h b/tools/f2fs_io/f2fs_io.h
index f2d0a0827ca5..21fd3864a20d 100644
--- a/tools/f2fs_io/f2fs_io.h
+++ b/tools/f2fs_io/f2fs_io.h
@@ -95,7 +95,7
On 03/07, Matthew Wilcox (Oracle) wrote:
> I was planning on sending this next cycle, but maybe there's time to
> squeeze these patches into the upcoming merge window?
>
> f2fs already implements writepages and migrate_folio for all three
> address_space_operations, so either ->writepage will neve
I meant let's support it conservatively if someone needs to enable
in other platform.
On 03/07, Chao Yu wrote:
> Let's disable nat_bits by default.
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/node.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> in
On 03/05, Chao Yu wrote:
> This patch turns off nat_bits feature by default in Android,
> for other scenario, keep it on and keep an eye on it.
>
> Signed-off-by: Chao Yu
> ---
> fsck/mount.c| 3 ++-
> include/f2fs_fs.h | 6 ++
> mkfs/f2fs_format.c | 3 ++-
> mkfs/f2fs
1 - 100 of 1228 matches
Mail list logo
