From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Nanzhe Zhao <zhaonanzhe@xiaomi.com>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Barry Song <baohua@kernel.org>, Juan Yescas <jyescas@google.com>,
Dev Jain <Dev.Jain@arm.com>,
linux-kernel@vger.kernel.org,
David Hildenbrand <David.Hildenbrand@arm.com>,
Bo Zhang <zhangbo56@xiaomi.com>,
Kalesh Singh <kaleshsingh@google.com>,
Nanzhe Zhao <nzzhao@126.com>, Pengfei Li <lipengfei28@xiaomi.com>,
Ryan Roberts <Ryan.Roberts@arm.com>
Subject: Re: [f2fs-dev] [PATCH 12/14] f2fs: handle block cloning within the same large folio
Date: Mon, 31 Aug 2026 16:19:05 +0800 [thread overview]
Message-ID: <f1ffd3a5-9fdc-4f26-bd9d-5f55e563f800@kernel.org> (raw)
In-Reply-To: <20260826130916.2231342-2-zhaonanzhe@xiaomi.com>
On 8/26/26 21:09, Nanzhe Zhao wrote:
> With large folios, the source and destination block in __clone_blkaddrs()
> can belong to the same folio during same-inode operations such as
> collapse range and insert range.
>
> In that case, locking the source folio and then looking up the
> destination folio can try to lock the same folio again. It also copies
> from and to offset 0, which is only correct for order-0 folios.
>
> Detect the same-inode, same-folio case before looking up the destination
> folio. Then in this case,we reserve the destination block explicitly.
>
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> ---
> fs/f2fs/file.c | 76 ++++++++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 64 insertions(+), 12 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 4272013dbe38..b82acbc3240f 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -1581,25 +1581,77 @@ static int __clone_blkaddrs(struct inode *src_inode, struct inode *dst_inode,
> f2fs_put_dnode(&dn);
> } else {
> struct folio *fsrc, *fdst;
> + size_t src_off, dst_off;
>
> fsrc = f2fs_get_lock_data_folio(src_inode,
> src + i, true);
> if (IS_ERR(fsrc))
> return PTR_ERR(fsrc);
> - fdst = f2fs_get_new_data_folio(dst_inode, NULL, dst + i,
> - true);
> - if (IS_ERR(fdst)) {
> - f2fs_folio_put(fsrc, true);
> - return PTR_ERR(fdst);
> - }
>
> - f2fs_folio_wait_writeback(fdst, DATA, true, true);
> + src_off = offset_in_folio(fsrc,
> + (loff_t)(src + i) << PAGE_SHIFT);
> +
> + /*
> + * For same-inode operations (collapse/insert), src and
> + * dst may fall within the same large folio. Detect this
> + * to avoid self-deadlock on folio lock.
> + */
> + if (src_inode == dst_inode &&
> + folio_contains(fsrc, dst + i)) {
> + struct dnode_of_data dn;
A lot of codes are redundant, can we add fdst = fsrc;
So that we can replace fsrc w/ fdst, and clean up the redundant codes blow:
Thanks,
> +
> + /* Reserve block for dst before copying */
> + set_new_dnode(&dn, dst_inode, NULL, NULL, 0);
> + ret = f2fs_reserve_block(&dn, dst + i);
> + if (ret) {
> + f2fs_folio_put(fsrc, true);
> + return ret;
> + }
> +
> + dst_off = offset_in_folio(fsrc,
> + (loff_t)(dst + i) << PAGE_SHIFT);
> + f2fs_folio_wait_writeback(fsrc, DATA, true, true);
> + memcpy_folio(fsrc, dst_off, fsrc, src_off,
> + PAGE_SIZE);
> + if (folio_test_large(fsrc)) {
> + f2fs_ffs_find_or_alloc(fsrc);
> + f2fs_ffs_mark_subrange_uptodate(fsrc,
> + dst_off, PAGE_SIZE);
> + f2fs_ffs_mark_subrange_dirty(fsrc, dst_off,
> + PAGE_SIZE);
> + }
> + folio_mark_dirty(fsrc);
> + if (i_size_read(dst_inode) <
> + ((loff_t)(dst + i + 1) << PAGE_SHIFT))
> + f2fs_i_size_write(dst_inode,
> + ((loff_t)(dst + i + 1) << PAGE_SHIFT));
> + folio_set_f2fs_gcing(fsrc);
> + f2fs_folio_put(fsrc, true);
> + } else {
> + fdst = f2fs_get_new_data_folio(dst_inode, NULL,
> + dst + i, true);
> + if (IS_ERR(fdst)) {
> + f2fs_folio_put(fsrc, true);
> + return PTR_ERR(fdst);
> + }
>
> - memcpy_folio(fdst, 0, fsrc, 0, PAGE_SIZE);
> - folio_mark_dirty(fdst);
> - folio_set_f2fs_gcing(fdst);
> - f2fs_folio_put(fdst, true);
> - f2fs_folio_put(fsrc, true);
> + dst_off = offset_in_folio(fdst,
> + (loff_t)(dst + i) << PAGE_SHIFT);
> + f2fs_folio_wait_writeback(fdst, DATA, true, true);
> + memcpy_folio(fdst, dst_off, fsrc, src_off,
> + PAGE_SIZE);
> + if (folio_test_large(fdst)) {
> + f2fs_ffs_find_or_alloc(fdst);
> + f2fs_ffs_mark_subrange_uptodate(fdst,
> + dst_off, PAGE_SIZE);
> + f2fs_ffs_mark_subrange_dirty(fdst, dst_off,
> + PAGE_SIZE);
> + }
> + folio_mark_dirty(fdst);
> + folio_set_f2fs_gcing(fdst);
> + f2fs_folio_put(fdst, true);
> + f2fs_folio_put(fsrc, true);
> + }
>
> ret = f2fs_truncate_hole(src_inode,
> src + i, src + i + 1);
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-08-31 8:19 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 8:26 [f2fs-dev] [PATCH 00/14] f2fs: support & optimize large folios for writable files Nanzhe Zhao via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 01/14] f2fs: extend folio state for large folio write path Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 6:57 ` Chao Yu via Linux-f2fs-devel
2026-08-27 20:51 ` Daeho Jeong
2026-09-04 3:44 ` Daeho Jeong
2026-09-07 6:49 ` Nanzhe Zhao
2026-09-07 9:31 ` Nanzhe Zhao
2026-09-09 20:25 ` Daeho Jeong
2026-09-08 3:41 ` Nanzhe Zhao
2026-08-26 8:26 ` [f2fs-dev] [PATCH 02/14] f2fs: carry subpage offset and count in write IO Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 7:16 ` Chao Yu via Linux-f2fs-devel
2026-08-27 21:06 ` Daeho Jeong
2026-08-26 8:26 ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes on large folios Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 8:56 ` Chao Yu via Linux-f2fs-devel
2026-08-27 21:13 ` Daeho Jeong
2026-09-07 3:51 ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes Nanzhe Zhao
2026-09-07 6:59 ` Chao Yu via Linux-f2fs-devel
2026-09-07 11:58 ` Nanzhe Zhao
2026-09-07 13:03 ` Nanzhe Zhao
2026-09-09 8:41 ` Chao Yu via Linux-f2fs-devel
2026-09-09 20:40 ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes on large folios Daeho Jeong
2026-09-10 10:33 ` Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 3:04 ` Chao Yu via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 04/14] f2fs: support atomic file large folios buffered write Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 9:24 ` Chao Yu via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 05/14] f2fs: support large folio writeback Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 11:17 ` Chao Yu via Linux-f2fs-devel
2026-08-27 22:39 ` Daeho Jeong
2026-09-04 4:04 ` Daeho Jeong
2026-09-04 4:07 ` Daeho Jeong
2026-09-07 3:57 ` Nanzhe Zhao
2026-09-09 21:03 ` Daeho Jeong
2026-09-07 10:12 ` Nanzhe Zhao
2026-09-09 21:08 ` Daeho Jeong
2026-09-07 3:51 ` Nanzhe Zhao
2026-09-07 6:59 ` Chao Yu via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 06/14] f2fs: prepare mmap write faults for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 12:36 ` Chao Yu via Linux-f2fs-devel
2026-08-28 17:18 ` Daeho Jeong
2026-09-07 7:34 ` Nanzhe Zhao
2026-09-09 7:34 ` Chao Yu via Linux-f2fs-devel
2026-09-09 21:22 ` Daeho Jeong
2026-08-26 8:26 ` [f2fs-dev] [PATCH 07/14] f2fs: make GC migration large-folio aware Nanzhe Zhao via Linux-f2fs-devel
2026-08-28 17:20 ` Daeho Jeong
2026-09-07 11:45 ` Nanzhe Zhao
2026-09-09 19:33 ` Daeho Jeong
2026-08-31 3:14 ` Chao Yu via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 08/14] f2fs: optimize small block size large folio read Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 4:21 ` Chao Yu via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 09/14] f2fs: support partial uptodate " Nanzhe Zhao via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 10/14] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 7:46 ` Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [f2fs-dev] [PATCH 11/14] f2fs: fix zeroing paths for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 7:56 ` Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [f2fs-dev] [PATCH 12/14] f2fs: handle block cloning within the same large folio Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 8:19 ` Chao Yu via Linux-f2fs-devel [this message]
2026-09-07 9:57 ` Nanzhe Zhao
2026-09-07 10:24 ` Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [f2fs-dev] [PATCH 13/14] f2fs: allow large folio support to writeable files Nanzhe Zhao via Linux-f2fs-devel
2026-08-28 17:44 ` Daeho Jeong
2026-09-07 6:33 ` Nanzhe Zhao
2026-09-09 19:23 ` Daeho Jeong
2026-08-31 8:31 ` Chao Yu via Linux-f2fs-devel
2026-09-07 11:14 ` Nanzhe Zhao
2026-08-26 13:09 ` [f2fs-dev] [PATCH 14/14] f2fs: make compressed files compatible with large folio Nanzhe Zhao via Linux-f2fs-devel
2026-08-28 17:52 ` Daeho Jeong
2026-09-07 3:45 ` Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 8:46 ` Chao Yu via Linux-f2fs-devel
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=f1ffd3a5-9fdc-4f26-bd9d-5f55e563f800@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=David.Hildenbrand@arm.com \
--cc=Dev.Jain@arm.com \
--cc=Ryan.Roberts@arm.com \
--cc=baohua@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jyescas@google.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lipengfei28@xiaomi.com \
--cc=nzzhao@126.com \
--cc=zhangbo56@xiaomi.com \
--cc=zhaonanzhe@xiaomi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.