From: Jeff Layton <jlayton@kernel.org>
To: lsf-pc <lsf-pc@lists.linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>
Subject: [LSF/MM/BPF TOPIC] inode timestamps and change cookie
Date: Wed, 28 Feb 2024 07:11:02 -0500 [thread overview]
Message-ID: <d16f4e3ca5dcf272316914312e531a484c8a5fcc.camel@kernel.org> (raw)
Last year, I led a discussion at LSF about the inode change cookie value
(aka i_version).
The original impetus for this work was the fact that all 3 mainstream
local filesystems (btrfs, ext4 and xfs) updated the value for different
sorts of activity, which can cause wildly different behavior when the
filesystem is exported via NFS. My hope last year was that we could fix
this with multigrain timestamps [1], but that didn't pan out.
At LSF, I'd like to give a brief overview of state of i_version work,
and lead a discussion on what work remains.
[1]: https://lwn.net/Articles/938240/
Thanks!
--
Jeff Layton <jlayton@kernel.org>
reply other threads:[~2024-02-28 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d16f4e3ca5dcf272316914312e531a484c8a5fcc.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).