From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jan Prusakowski <jprusakowski@google.com>, fstests@vger.kernel.org
Cc: jaegeuk@kernel.org, zlang@kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] generic/064: allow 50 extents on F2FS after fcollapse
Date: Tue, 23 Jun 2026 16:46:29 +0800 [thread overview]
Message-ID: <698bcb3a-38d8-479a-b0e0-13d23a08743d@kernel.org> (raw)
In-Reply-To: <20260622070438.1542638-1-jprusakowski@google.com>
On 6/22/26 15:04, Jan Prusakowski via Linux-f2fs-devel wrote:
> On F2FS, generic/064 fails with "extents mismatched before = 1 after =
> 50" following multiple fcollapse (collapse range) operations.
>
> To ensure crash consistency and checkpoint integrity, F2FS forbids
> in-place SSR (Summary Standalone Replacement) overwrites on valid
> checkpointed blocks. When collapse range shifts blocks, F2FS allocates
> new data pages in LFS mode (out-of-place log writes). As a result,
> sequential collapse range calls rewrite shifted blocks at new log
> locations, intentionally leaving the file with 50 extents.
>
> Adjust the extent verification in generic/064 to expect exactly 50
> extents on F2FS, while preserving the strict 1-extent requirement for
> all other filesystems. Data integrity continues to be verified via byte
> comparison.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> Signed-off-by: Jan Prusakowski <jprusakowski@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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-06-23 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 7:04 [f2fs-dev] [PATCH] generic/064: allow 50 extents on F2FS after fcollapse Jan Prusakowski via Linux-f2fs-devel
2026-06-23 8:46 ` Chao Yu via Linux-f2fs-devel [this message]
2026-06-24 7:46 ` Christoph Hellwig
2026-06-29 16:37 ` Zorro Lang via Linux-f2fs-devel
2026-06-30 12:09 ` Chao Yu via Linux-f2fs-devel
2026-07-19 9:24 ` Zorro Lang via Linux-f2fs-devel
2026-07-22 1:22 ` Chao Yu via Linux-f2fs-devel
2026-07-20 8:04 ` Christoph Hellwig
2026-07-22 1:12 ` Chao Yu via Linux-f2fs-devel
2026-07-22 8:59 ` Christoph Hellwig
2026-07-22 12:32 ` 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=698bcb3a-38d8-479a-b0e0-13d23a08743d@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jprusakowski@google.com \
--cc=zlang@kernel.org \
/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