From: Wenjie Qi <qwjhust@gmail.com>
To: jaegeuk@kernel.org, chao@kernel.org
Cc: daeho43@gmail.com, daehojeong@google.com, sunqiuyang@huawei.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, qiwenjie@xiaomi.com,
qwjhust@gmail.com
Subject: [PATCH v4 0/2] f2fs: fix online resize state
Date: Fri, 16 Oct 2026 13:44:04 +0800 [thread overview]
Message-ID: <cover.1792116883.git.qiwenjie@xiaomi.com> (raw)
Online shrink changes both persistent SIT state and the geometry used
by pinned allocation. This series keeps those states consistent during
range evacuation and after the geometry changes.
Patch 1 drains the SIT journal during resize even when there are no
new dirty sentries. It is unchanged and retains Daeho's Reviewed-by.
Patch 2 consumes the tail reservation, refreshes the pinned boundary,
and restores both on final checkpoint rollback. It also limits pinned
allocation by the temporarily reduced MAIN_SECS() during evacuation.
Changes in v4 (since v3):
- Bound pinned section allocation by the current MAIN_SECS().
Changes in v3 (since v2):
- Rebase onto f2fs/dev.
- Reduce resizable_tail_secno by the removed sections, down to zero.
- Save the current tail after freeze and restore it on rollback.
- Document that online shrink consumes the reservation.
- Retain Daeho's review for patch 1; request a new review for patch 2.
Changes in v2 (since v1):
- Simplify tail validation and improve rejection diagnostics.
- Validate before taking the mount write reference and recheck
after freeze for concurrent remounts.
v1:
- Initial SIT-journal and pinned-boundary fixes.
Wenjie Qi (2):
f2fs: flush SIT journal during filesystem resize
f2fs: refresh pinned allocation boundary after resize
Documentation/filesystems/f2fs.rst | 3 ++-
fs/f2fs/gc.c | 6 +++++-
fs/f2fs/segment.c | 4 ++--
fs/f2fs/segment.h | 11 +++++++++++
fs/f2fs/super.c | 15 ++-------------
5 files changed, 22 insertions(+), 17 deletions(-)
base-commit: e455328a66a5f4827d4ba96acfe50dbbb0e13b8d
--
2.43.0
next reply other threads:[~2026-10-16 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 5:44 Wenjie Qi [this message]
2026-10-16 5:44 ` [PATCH v4 1/2] f2fs: flush SIT journal during filesystem resize Wenjie Qi
2026-10-16 5:44 ` [PATCH v4 2/2] f2fs: refresh pinned allocation boundary after resize Wenjie Qi
2026-10-16 13:50 ` Daeho Jeong
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=cover.1792116883.git.qiwenjie@xiaomi.com \
--to=qwjhust@gmail.com \
--cc=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=qiwenjie@xiaomi.com \
--cc=sunqiuyang@huawei.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®