From: Jeff Layton <jlayton@kernel.org>
To: Pankaj Raghav <p.raghav@samsung.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, Andres Freund <andres@anarazel.de>,
Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, hch@lst.de,
open list <linux-kernel@vger.kernel.org>,
pankaj.raghav@linux.dev, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] fs: fix forced iversion increment on lazytime timestamp updates
Date: Mon, 11 May 2026 07:24:21 -0400 [thread overview]
Message-ID: <46670e8eb6306f7d528841f85a46a44e5790459a.camel@kernel.org> (raw)
In-Reply-To: <20260511111918.1793689-1-p.raghav@samsung.com>
On Mon, 2026-05-11 at 13:19 +0200, Pankaj Raghav wrote:
> When updating timestamps with lazytime enabled, if only I_DIRTY_TIME is
> set (pure lazytime update), inode_maybe_inc_iversion() should not be
> forced to increment i_version. The force parameter should only be true
> when actual data or metadata changes require an iversion bump.
>
> The current code uses "!!dirty" which evaluates to true whenever dirty
> has any bits set, including the I_DIRTY_TIME bit alone. This forces an
> iversion increment on every lazytime timestamp update, which then sets
> I_DIRTY_SYNC, triggering expensive log flushes on subsequent fdatasync
> calls. Andres reported this issue when he noticed a perf regression[1].
>
> Fix this by using "dirty != I_DIRTY_TIME" as the force parameter. This
> passes false for pure lazytime updates (allowing the I_VERSION_QUERIED
> optimization to work), while still forcing the increment when dirty
> contains other flags indicating real changes that require iversion
> updates.
>
> [1] https://lore.kernel.org/linux-xfs/7ys6erh3nnyeerv2nybyfvp7dmaknuxrlxv74wx56ocdothkc6@ekfiadtkfn2r/
>
> Fixes: 85c871a02b03 ("fs: add support for non-blocking timestamp updates")
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
> fs/inode.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/fs/inode.c b/fs/inode.c
> index 6a3cbc7dcd28..62c579a0cf7d 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -2124,7 +2124,13 @@ static int inode_update_cmtime(struct inode *inode, unsigned int flags)
> inode_iversion_need_inc(inode))
> return -EAGAIN;
> } else {
> - if (inode_maybe_inc_iversion(inode, !!dirty))
> + /*
> + * Don't force iversion increment for pure lazytime
> + * updates (I_DIRTY_TIME only), let I_VERSION_QUERIED
> + * dictate whether the increment is needed.
> + */
> + if (inode_maybe_inc_iversion(inode,
> + dirty != I_DIRTY_TIME))
> dirty |= I_DIRTY_SYNC;
> }
> }
>
> base-commit: 4cd074ae20bbcc293bbbce9163abe99d68ae6ae0
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-05-11 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 11:19 [PATCH] fs: fix forced iversion increment on lazytime timestamp updates Pankaj Raghav
2026-05-11 11:24 ` Jeff Layton [this message]
2026-05-11 12:10 ` Christoph Hellwig
2026-05-11 12:12 ` Carlos Maiolino
2026-05-11 13:32 ` Christian Brauner
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=46670e8eb6306f7d528841f85a46a44e5790459a.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=andres@anarazel.de \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=pankaj.raghav@linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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