From: Chao Yu <chao@kernel.org>
To: Nanzhe Zhao <zhaonanzhe@xiaomi.com>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, Daeho Jeong <daehojeong@google.com>,
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: [PATCH v3 04/17] f2fs: support atomic file large folios buffered write
Date: Mon, 12 Oct 2026 11:06:27 +0800 [thread overview]
Message-ID: <e12debf8-87d0-4c17-8973-98e950c2047f@kernel.org> (raw)
In-Reply-To: <20261009161224.4163796-5-zhaonanzhe@xiaomi.com>
On 10/10/26 00:12, Nanzhe Zhao wrote:
> + /* If index is beyond the end of file, reserve a new block in COW inode */
> + if ((index << PAGE_SHIFT) >= i_size_read(inode))
Can you please check all "xxx << PAGE_SHIFT" statements in patchset to see if there
is overflow issue?
> + if (f2fs_folio_may_unlock_balance_fs(folio, mapping, need_balance)) {
> folio_unlock(folio);
> - f2fs_balance_fs(sbi, true);
> - folio_lock(folio);
> - if (folio->mapping != mapping) {
> - /* The folio got truncated from under us */
> - folio_unlock(folio);
> - folio_put(folio);
> - goto repeat;
> - }
> + folio_put(folio);
Then we can call f2fs_folio_put(, true) to clean up the codes?
> if (folio_test_large(folio)) {
> - err = prepare_large_folio_write_begin(inode,
> + if (f2fs_is_atomic_file(inode))
> + err = prepare_large_folio_atomic_write_begin(inode,
> + mapping, folio, pos, len);
> + else
> + err = prepare_large_folio_write_begin(inode,
> folio, pos, blen);
Same question as it in 03/17, can we relocate?
Thanks,
next prev parent reply other threads:[~2026-10-12 3:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 16:12 [PATCH v3 00/17] f2fs: support & optimize large folios for writable files Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 01/17] f2fs: extend folio state for large folio write path Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 02/17] f2fs: carry subpage offset and count in write IO Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 03/17] f2fs: support regular file buffered writes on large folios Nanzhe Zhao
2026-10-09 18:34 ` [f2fs-dev] " Daeho Jeong
2026-10-10 10:02 ` Nanzhe Zhao
2026-10-12 3:01 ` Chao Yu
2026-10-12 13:06 ` [f2fs-dev] " Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 04/17] f2fs: support atomic file large folios buffered write Nanzhe Zhao
2026-10-12 3:06 ` Chao Yu [this message]
2026-10-09 16:12 ` [PATCH v3 05/17] f2fs: support large folio writeback Nanzhe Zhao
2026-10-12 4:36 ` Chao Yu
2026-10-09 16:12 ` [PATCH v3 06/17] f2fs: account large folio dirty data at block granularity Nanzhe Zhao
2026-10-12 6:54 ` Chao Yu
2026-10-09 16:12 ` [PATCH v3 07/17] f2fs: remove mappedtodisk flag usage in mmap write path Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 08/17] f2fs: prepare mmap write faults for large folios Nanzhe Zhao
2026-10-12 7:04 ` Chao Yu
2026-10-09 16:12 ` [PATCH v3 09/17] f2fs: make GC migration large-folio aware Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 10/17] f2fs: optimize small block size large folio read Nanzhe Zhao
2026-10-12 7:09 ` Chao Yu
2026-10-09 16:28 ` [PATCH v3 11/17] f2fs: support partial uptodate " Nanzhe Zhao
2026-10-12 7:18 ` Chao Yu
2026-10-09 16:28 ` [PATCH v3 12/17] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao
2026-10-09 18:14 ` [f2fs-dev] " Daeho Jeong
2026-10-12 7:27 ` Chao Yu
2026-10-09 16:28 ` [PATCH v3 13/17] f2fs: wait for folio writeback before ffs_detach_free Nanzhe Zhao
2026-10-09 16:28 ` [PATCH v3 14/17] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-10-09 16:28 ` [PATCH v3 15/17] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-10-09 16:28 ` [PATCH v3 16/17] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-10-09 16:28 ` [PATCH v3 17/17] f2fs: make compressed files compatible with large folio Nanzhe Zhao
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=e12debf8-87d0-4c17-8973-98e950c2047f@kernel.org \
--to=chao@kernel.org \
--cc=David.Hildenbrand@arm.com \
--cc=Dev.Jain@arm.com \
--cc=Ryan.Roberts@arm.com \
--cc=baohua@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=jyescas@google.com \
--cc=kaleshsingh@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 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®