From: Chao Yu <chao@kernel.org>
To: wangzijie <wangzijie1@honor.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, bintian.wang@honor.com,
feng.han@honor.com
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: fix zero-sized extent for precache extents
Date: Wed, 17 Sep 2025 14:41:38 +0800 [thread overview]
Message-ID: <760669e9-22ec-490f-adc2-2981d2a56709@kernel.org> (raw)
In-Reply-To: <20250917023622.516052-1-wangzijie1@honor.com>
On 9/17/25 10:36, 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 like this:
> dnode1: dnode2:
> [0] A [0] NEW_ADDR
> [1] A+1 [1] 0x0
> ...
> [1016] A+1016
> [1017] B (B!=A+1017) [1017] 0x0
>
> During precache_extents, we map the last block(valid blkaddr) in dnode1:
> map->m_flags |= F2FS_MAP_MAPPED;
> map->m_pblk = blkaddr(valid blkaddr);
> map->m_len = 1;
> then we goto next_dnode, meet the first block in dnode2(hole), goto sync_out:
> map->m_flags & F2FS_MAP_MAPPED == true, and we make zero-sized extent:
>
> map->m_len = 1
> ofs = start_pgofs - map->m_lblk = 1882 - 1881 = 1
> ei.fofs = start_pgofs = 1882
> ei.len = map->m_len - ofs = 1 - 1 = 0
>
>
> Rebased on patch[1], this patch can cover these cases to avoid zero-sized extent:
> A,B,C is valid blkaddr
> case1:
> dnode1: dnode2:
> [0] A [0] NEW_ADDR
> [1] A+1 [1] 0x0
> ... ....
> [1016] A+1016
> [1017] B (B!=A+1017) [1017] 0x0
>
> case2:
> dnode1: dnode2:
> [0] A [0] C (C!=B+1)
> [1] A+1 [1] C+1
> ... ....
> [1016] A+1016
> [1017] B (B!=A+1017) [1017] 0x0
>
> case3:
> dnode1: dnode2:
> [0] A [0] C (C!=B+2)
> [1] A+1 [1] C+1
> ... ....
> [1015] A+1015
> [1016] B (B!=A+1016)
> [1017] B+1 [1017] 0x0
>
> [1] https://lore.kernel.org/linux-f2fs-devel/20250912081250.44383-1-chao@kernel.org/
>
> Fixes: c4020b2da4c9 ("f2fs: support F2FS_IOC_PRECACHE_EXTENTS")
> Signed-off-by: wangzijie <wangzijie1@honor.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-09-17 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 2:36 wangzijie
2025-09-17 2:36 ` [f2fs-dev] [PATCH v3 2/2] f2fs: fix infinite loop in __insert_extent_tree() wangzijie
2025-09-17 6:48 ` Chao Yu
2025-09-17 6:41 ` Chao Yu [this message]
2025-09-17 15:59 ` [f2fs-dev] [PATCH v3 1/2] f2fs: fix zero-sized extent for precache extents Jaegeuk Kim
2025-09-29 22:30 ` patchwork-bot+f2fs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=760669e9-22ec-490f-adc2-2981d2a56709@kernel.org \
--to=chao@kernel.org \
--cc=bintian.wang@honor.com \
--cc=feng.han@honor.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzijie1@honor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®