From: Jeff Layton <jlayton@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Chandan Babu R <chandan.babu@oracle.com>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Dave Chinner <david@fromorbit.com>,
Andi Kleen <ak@linux.intel.com>,
Christoph Hellwig <hch@infradead.org>,
Uros Bizjak <ubizjak@gmail.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
kernel-team@fb.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-mm@kvack.org, linux-nfs@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 6/9] xfs: switch to multigrain timestamps
Date: Mon, 08 Jul 2024 14:51:07 -0400 [thread overview]
Message-ID: <28e7a6c193674f2aa41ab1eec9bb8747ddba1a4c.camel@kernel.org> (raw)
In-Reply-To: <20240708184739.GP612460@frogsfrogsfrogs>
On Mon, 2024-07-08 at 11:47 -0700, Darrick J. Wong wrote:
> On Mon, Jul 08, 2024 at 11:53:39AM -0400, Jeff Layton wrote:
> > Enable multigrain timestamps, which should ensure that there is an
> > apparent change to the timestamp whenever it has been written after
> > being actively observed via getattr.
> >
> > Also, anytime the mtime changes, the ctime must also change, and those
> > are now the only two options for xfs_trans_ichgtime. Have that function
> > unconditionally bump the ctime, and ASSERT that XFS_ICHGTIME_CHG is
> > always set.
> >
> > Finally, stop setting STATX_CHANGE_COOKIE in getattr, since the ctime
> > should give us better semantics now.
> >
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > fs/xfs/libxfs/xfs_trans_inode.c | 6 +++---
> > fs/xfs/xfs_iops.c | 10 +++-------
> > fs/xfs/xfs_super.c | 2 +-
> > 3 files changed, 7 insertions(+), 11 deletions(-)
> >
> > diff --git a/fs/xfs/libxfs/xfs_trans_inode.c b/fs/xfs/libxfs/xfs_trans_inode.c
> > index 69fc5b981352..1f3639bbf5f0 100644
> > --- a/fs/xfs/libxfs/xfs_trans_inode.c
> > +++ b/fs/xfs/libxfs/xfs_trans_inode.c
> > @@ -62,12 +62,12 @@ xfs_trans_ichgtime(
> > ASSERT(tp);
> > xfs_assert_ilocked(ip, XFS_ILOCK_EXCL);
> >
> > - tv = current_time(inode);
> > + /* If the mtime changes, then ctime must also change */
> > + ASSERT(flags & XFS_ICHGTIME_CHG);
> >
> > + tv = inode_set_ctime_current(inode);
> > if (flags & XFS_ICHGTIME_MOD)
> > inode_set_mtime_to_ts(inode, tv);
> > - if (flags & XFS_ICHGTIME_CHG)
> > - inode_set_ctime_to_ts(inode, tv);
> > if (flags & XFS_ICHGTIME_CREATE)
> > ip->i_crtime = tv;
> > }
> > diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> > index a00dcbc77e12..d25872f818fa 100644
> > --- a/fs/xfs/xfs_iops.c
> > +++ b/fs/xfs/xfs_iops.c
> > @@ -592,8 +592,9 @@ xfs_vn_getattr(
> > stat->gid = vfsgid_into_kgid(vfsgid);
> > stat->ino = ip->i_ino;
> > stat->atime = inode_get_atime(inode);
> > - stat->mtime = inode_get_mtime(inode);
> > - stat->ctime = inode_get_ctime(inode);
> > +
> > + fill_mg_cmtime(stat, request_mask, inode);
>
> Sooo... for setting up a commit-range operation[1], XFS_IOC_START_COMMIT
> could populate its freshness data by calling:
>
> struct kstat dummy;
>
> fill_mg_ctime(&dummy, STATX_CTIME | STATX_MTIME, inode);
>
> and then using dummy.[cm]time to populate the freshness data that it
> gives to userspace, right? Having set QUERIED, a write to the file
> immediately afterwards will cause a (tiny) increase in ctime_nsec which
> will cause the XFS_IOC_COMMIT_RANGE to reject the commit[2]. Right?
>
Yes. Once you call fill_mg_ctime, the first write after that point
should cause the kernel to ensure that there is a distinct change in
the ctime.
IOW, I think this should alleviate the concerns I had before with using
timestamps with the XFS_IOC_COMMIT_RANGE interface.
> --D
>
> [1] https://lore.kernel.org/linux-xfs/20240227174649.GL6184@frogsfrogsfrogs/
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?h=atomic-file-commits&id=0520d89c2698874c1f56ddf52ec4b8a3595baa14
>
> > +
> > stat->blocks = XFS_FSB_TO_BB(mp, ip->i_nblocks + ip->i_delayed_blks);
> >
> > if (xfs_has_v3inodes(mp)) {
> > @@ -603,11 +604,6 @@ xfs_vn_getattr(
> > }
> > }
> >
> > - if ((request_mask & STATX_CHANGE_COOKIE) && IS_I_VERSION(inode)) {
> > - stat->change_cookie = inode_query_iversion(inode);
> > - stat->result_mask |= STATX_CHANGE_COOKIE;
> > - }
> > -
> > /*
> > * Note: If you add another clause to set an attribute flag, please
> > * update attributes_mask below.
> > diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> > index 27e9f749c4c7..210481b03fdb 100644
> > --- a/fs/xfs/xfs_super.c
> > +++ b/fs/xfs/xfs_super.c
> > @@ -2052,7 +2052,7 @@ static struct file_system_type xfs_fs_type = {
> > .init_fs_context = xfs_init_fs_context,
> > .parameters = xfs_fs_parameters,
> > .kill_sb = xfs_kill_sb,
> > - .fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP,
> > + .fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP | FS_MGTIME,
> > };
> > MODULE_ALIAS_FS("xfs");
> >
> >
> > --
> > 2.45.2
> >
> >
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-07-08 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 15:53 [PATCH v4 0/9] fs: multigrain timestamp redux Jeff Layton
2024-07-08 15:53 ` [PATCH v4 1/9] fs: add infrastructure for multigrain timestamps Jeff Layton
2024-07-08 18:39 ` Darrick J. Wong
2024-07-08 18:47 ` Jeff Layton
2024-07-08 15:53 ` [PATCH v4 2/9] fs: tracepoints around multigrain timestamp events Jeff Layton
2024-07-08 15:53 ` [PATCH v4 3/9] fs: add percpu counters for significant " Jeff Layton
2024-07-08 15:53 ` [PATCH v4 4/9] fs: have setattr_copy handle multigrain timestamps appropriately Jeff Layton
2024-07-08 15:53 ` [PATCH v4 5/9] Documentation: add a new file documenting multigrain timestamps Jeff Layton
2024-07-09 23:50 ` Randy Dunlap
2024-07-08 15:53 ` [PATCH v4 6/9] xfs: switch to " Jeff Layton
2024-07-08 18:47 ` Darrick J. Wong
2024-07-08 18:51 ` Jeff Layton [this message]
2024-07-08 19:00 ` Jeff Layton
2024-07-08 19:01 ` Darrick J. Wong
2024-07-08 15:53 ` [PATCH v4 7/9] ext4: " Jeff Layton
2024-07-08 15:53 ` [PATCH v4 8/9] btrfs: convert " Jeff Layton
2024-07-08 15:53 ` [PATCH v4 9/9] tmpfs: add support for " 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=28e7a6c193674f2aa41ab1eec9bb8747ddba1a4c.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=clm@fb.com \
--cc=corbet@lwn.net \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kent.overstreet@linux.dev \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
--cc=ubizjak@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).