[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176962347636.1138505.14797940787687720541.b4-ty@mit.edu>
Date: Wed, 28 Jan 2026 13:05:05 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: Andreas Dilger <adilger.kernel@...ger.ca>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, Li Chen <me@...ux.beauty>
Cc: "Theodore Ts'o" <tytso@....edu>
Subject: Re: [RFC 0/5] ext4: mark more ops fast-commit ineligible
On Thu, 11 Dec 2025 19:51:37 +0800, Li Chen wrote:
> 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.
>
> [...]
Applied, thanks!
[1/5] ext4: mark inode format migration fast-commit ineligible
commit: 87e79fa122bc9a6576f1690ee264fcbd77d3ab58
[2/5] ext4: mark fs-verity enable fast-commit ineligible
commit: 16d43b9748c655b36a675cc55789f40fd827e9b1
[3/5] ext4: mark move extents fast-commit ineligible
commit: 690558921d9f9388c6bc83610451d8cb393e4d88
[4/5] ext4: mark group add fast-commit ineligible
commit: 89b4336fd5ec78f51f9d3a1d100f3ffa3228e604
[5/5] ext4: mark group extend fast-commit ineligible
commit: 1f8dd813a1c771b13c303f73d876164bc9b327cc
Best regards,
--
Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists