From: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>, 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 v2 10/14] f2fs: handle partial truncate of large folio dirty subpages
Date: Wed, 23 Sep 2026 10:50:35 +0800 [thread overview]
Message-ID: <20260923025035.2202070-1-zhaonanzhe@xiaomi.com> (raw)
In-Reply-To: <c4e0c6d3-ad28-4e5e-a938-08b7658e9931@kernel.org>
On Thu, 17 Sep 2026 16:30:59 +0800, Chao Yu wrote:
> Since gcing flag is per-folio, so if block #0 is on gcing, but block #1 is
> truncated, it will drop on gcing flag of folio, result in triggering IPU on
> such dirtied block of large folio? also it will affect f2fs_is_cp_guaranteed()?
Hi Chao,
Thanks for the review. I think I may should change like this?
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index f5421334ecf3..a94153be0533 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -351,6 +351,27 @@ static void f2fs_read_end_io(struct bio *bio)
f2fs_verify_and_finish_bio(bio, intask);
}
+static bool f2fs_ffs_has_dirty_subpage(struct folio *folio)
+{
+ struct f2fs_folio_state *ffs;
+ unsigned long flags;
+ unsigned int nr_subpages;
+ bool dirty;
+
+ if (!f2fs_folio_has_ffs(folio))
+ return false;
+
+ ffs = (struct f2fs_folio_state *)folio->private;
+ nr_subpages = folio_nr_pages(folio);
+
+ spin_lock_irqsave(&ffs->state_lock, flags);
+ dirty = find_next_bit(ffs->state, 2 * nr_subpages,
+ nr_subpages) < 2 * nr_subpages;
+ spin_unlock_irqrestore(&ffs->state_lock, flags);
+
+ return dirty;
+}
+
static void f2fs_write_end_bio(struct bio *bio)
{
struct f2fs_sb_info *sbi = bio->bi_private;
@@ -410,7 +431,8 @@ static void f2fs_write_end_bio(struct bio *bio)
wake_up(&sbi->cp_wait);
if (finished) {
- folio_clear_f2fs_gcing(folio);
+ if (!f2fs_ffs_has_dirty_subpage(folio))
+ folio_clear_f2fs_gcing(folio);
folio_end_writeback(folio);
}
}
@@ -3575,11 +3597,10 @@ static int f2fs_write_single_data_folio(struct folio *folio, int *submitted,
fio.old_blkaddr = dn.data_blkaddr;
/* This page is already truncated */
if (fio.old_blkaddr == NULL_ADDR) {
ffs_clear_subrange_uptodate(folio,
i << PAGE_SHIFT, PAGE_SIZE);
- folio_clear_f2fs_gcing(folio);
goto block_done;
}
@@ -4122,6 +4143,7 @@ static int f2fs_write_cache_folios(struct address_space *mapping,
bool verity_in_progress;
int folio_submitted = 0;
bool bias_added = false;
+ bool dirty;
submitted = 0;
next = true;
@@ -4224,15 +4246,19 @@ static int f2fs_write_cache_folios(struct address_space *mapping,
* partially written back), the folio must stay dirty so that
* the remaining subranges are written back later.
*/
- if (f2fs_ffs_clear_subrange_dirty_and_test(folio, 0,
- (err ? pos : end_pos) - folio_pos(folio)))
+ dirty = f2fs_ffs_clear_subrange_dirty_and_test(folio, 0,
+ (err ? pos : end_pos) - folio_pos(folio));
+ if (dirty)
folio_redirty_for_writepage(wbc, folio);
else
inode_dec_dirty_pages(inode);
if (bias_added) {
- if (atomic_dec_and_test(&ffs->write_pages_pending))
+ if (atomic_dec_and_test(&ffs->write_pages_pending)) {
+ if (!dirty)
+ folio_clear_f2fs_gcing(folio);
folio_end_writeback(folio);
+ }
} else if (!folio_submitted && folio_test_writeback(folio)) {
folio_end_writeback(folio);
}
@@ -5054,6 +5080,8 @@ void f2fs_invalidate_folio(struct folio *folio, size_t offset, size_t length)
f2fs_remove_dirty_inode(inode);
folio_cancel_dirty(folio);
}
+ if (!dirty && !folio_test_writeback(folio))
+ folio_clear_f2fs_gcing(folio);
return;
}
--
Nanzhe Zhao
next prev parent reply other threads:[~2026-09-23 2:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 4:18 [PATCH v2 00/14] f2fs: support & optimize large folios for writable files Nanzhe Zhao
2026-09-15 4:18 ` [PATCH v2 01/14] f2fs: extend folio state for large folio write path Nanzhe Zhao
2026-09-16 9:53 ` Chao Yu
2026-09-15 4:18 ` [PATCH v2 02/14] f2fs: carry subpage offset and count in write IO Nanzhe Zhao
2026-09-15 4:18 ` [PATCH v2 03/14] f2fs: support regular file buffered writes on large folios Nanzhe Zhao
2026-09-16 11:47 ` Chao Yu
2026-09-15 4:18 ` [PATCH v2 04/14] f2fs: support atomic file large folios buffered write Nanzhe Zhao
2026-09-16 12:07 ` Chao Yu
2026-09-23 3:21 ` [f2fs-dev] " Nanzhe Zhao
2026-09-23 7:22 ` Chao Yu
2026-09-15 4:19 ` [PATCH v2 05/14] f2fs: support large folio writeback Nanzhe Zhao
2026-09-17 3:48 ` Chao Yu
2026-09-21 2:52 ` Chao Yu
2026-09-15 4:19 ` [PATCH v2 06/14] f2fs: prepare mmap write faults for large folios Nanzhe Zhao
2026-09-17 6:32 ` Chao Yu
2026-09-15 4:19 ` [PATCH v2 07/14] f2fs: make GC migration large-folio aware Nanzhe Zhao
2026-09-15 4:19 ` [PATCH v2 08/14] f2fs: optimize small block size large folio read Nanzhe Zhao
2026-09-16 4:33 ` [f2fs-dev] " Daeho Jeong
2026-09-23 2:36 ` Nanzhe Zhao
2026-09-24 1:34 ` Nanzhe Zhao
2026-09-17 8:09 ` Chao Yu
2026-09-15 4:19 ` [PATCH v2 09/14] f2fs: support partial uptodate " Nanzhe Zhao
2026-09-15 4:19 ` [PATCH v2 10/14] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao
2026-09-17 8:30 ` Chao Yu
2026-09-23 2:50 ` Nanzhe Zhao [this message]
2026-09-23 7:18 ` [f2fs-dev] " Chao Yu
2026-09-17 8:32 ` Chao Yu
2026-09-15 4:25 ` [PATCH v2 11/14] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-09-15 4:25 ` [PATCH v2 12/14] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-09-15 4:25 ` [PATCH v2 13/14] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-09-17 14:07 ` Chao Yu
2026-09-15 4:25 ` [PATCH v2 14/14] f2fs: make compressed files compatible with large folio Nanzhe Zhao
2026-09-22 3:09 ` Chao Yu
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=20260923025035.2202070-1-zhaonanzhe@xiaomi.com \
--to=zhaonanzhe@xiaomi.com \
--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-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lipengfei28@xiaomi.com \
--cc=nzzhao@126.com \
--cc=zhangbo56@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®