From: Li Chen <me@linux.beauty>
To: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: [RFC 0/5] ext4: mark more ops fast-commit ineligible
Date: Thu, 11 Dec 2025 19:51:37 +0800 [thread overview]
Message-ID: <20251211115146.897420-1-me@linux.beauty> (raw)
ext4 fast commit only logs operations with replay support. This series
marks a few more operations as fast-commit ineligible and accounts
them via fc_info so behaviour under fast commit is easier to reason
about.
Testing was done in a QEMU guest on loopback ext4 filesystems created
with -O fast_commit[/,verity] by exercising each operation and checking
/proc/fs/ext4/*/fc_info for the corresponding ineligible reason and
ineligible commit counters. Detailed steps are in each commit's message.
Li Chen (5):
ext4: mark inode format migration fast-commit ineligible
ext4: mark fs-verity enable fast-commit ineligible
ext4: mark move extents fast-commit ineligible
ext4: mark group add fast-commit ineligible
ext4: mark group extend fast-commit ineligible
fs/ext4/fast_commit.c | 3 +++
fs/ext4/fast_commit.h | 3 +++
fs/ext4/ioctl.c | 3 +++
fs/ext4/migrate.c | 12 ++++++++++++
fs/ext4/move_extent.c | 1 +
fs/ext4/verity.c | 2 ++
include/trace/events/ext4.h | 8 +++++++-
7 files changed, 31 insertions(+), 1 deletion(-)
--
2.51.0
next reply other threads:[~2025-12-11 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 11:51 Li Chen [this message]
2025-12-11 11:51 ` [RFC 1/5] ext4: mark inode format migration fast-commit ineligible Li Chen
2025-12-11 11:51 ` [RFC 2/5] ext4: mark fs-verity enable " Li Chen
2025-12-11 11:51 ` [RFC 3/5] ext4: mark move extents " Li Chen
2025-12-11 11:51 ` [RFC 4/5] ext4: mark group add " Li Chen
2025-12-11 11:51 ` [RFC 5/5] ext4: mark group extend " Li Chen
2026-01-19 2:58 ` Theodore Tso
2026-01-19 3:03 ` Theodore Tso
2026-01-19 12:37 ` Li Chen
2026-01-28 18:05 ` [RFC 0/5] ext4: mark more ops " Theodore Ts'o
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=20251211115146.897420-1-me@linux.beauty \
--to=me@linux.beauty \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
/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