From: Jeff Layton <jlayton@kernel.org>
To: linux-xfs <linux-xfs@vger.kernel.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: replacement i_version counter for xfs
Date: Tue, 24 Jan 2023 07:56:09 -0500 [thread overview]
Message-ID: <57c413ed362c0beab06b5d83b7fc4b930c7662c4.camel@kernel.org> (raw)
A few months ago, I posted a patch to make xfs not bump its i_version
counter on atime updates. Dave Chinner NAK'ed that patch, mentioning
that xfs would need to replace it with an entirely new field as the
existing counter is used for other purposes and its semantics are set in
stone.
Has anything been done toward that end? Should I file a bug report or
something? It would be nice to get this going so that XFS can continue
to be a viable filesystem for exporting via NFS.
Thanks,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2023-01-24 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 12:56 Jeff Layton [this message]
2023-01-25 0:02 ` replacement i_version counter for xfs Dave Chinner
2023-01-25 11:47 ` Jeff Layton
2023-01-25 16:32 ` Darrick J. Wong
2023-01-25 17:58 ` Jeff Layton
2023-01-30 2:05 ` Dave Chinner
2023-01-31 12:02 ` Jeff Layton
2023-01-31 23:31 ` Dave Chinner
2023-02-01 19:19 ` Jeff Layton
2023-01-30 1:54 ` Dave Chinner
2023-01-31 11:55 ` Jeff Layton
2023-01-31 23:23 ` Dave Chinner
2023-02-01 19:11 ` Jeff Layton
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=57c413ed362c0beab06b5d83b7fc4b930c7662c4.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.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