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>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
Chuck Lever <chuck.lever@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-mm@kvack.org,
linux-nfs@vger.kernel.org
Subject: Re: [RFC PATCH 3/3][RESEND] xfs: mark the inode for high-res timestamp update in getattr
Date: Tue, 11 Apr 2023 11:58:34 -0400 [thread overview]
Message-ID: <75eebb5ddf9bd21df2782a87208dee2cda7e93e3.camel@kernel.org> (raw)
In-Reply-To: <20230411145446.GG360895@frogsfrogsfrogs>
On Tue, 2023-04-11 at 07:54 -0700, Darrick J. Wong wrote:
> On Tue, Apr 11, 2023 at 10:37:02AM -0400, Jeff Layton wrote:
> > When the mtime or ctime is being queried via getattr, ensure that we
> > mark the inode for a high-res timestamp update on the next pass. Also,
> > switch to current_cmtime for other c/mtime updates.
> >
> > With this change, we're better off having the NFS server just ignore
> > the i_version field and have it use the ctime instead, so clear the
> > STATX_CHANGE_COOKIE flag in the result mask in ->getattr.
> >
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > fs/xfs/libxfs/xfs_trans_inode.c | 2 +-
> > fs/xfs/xfs_acl.c | 2 +-
> > fs/xfs/xfs_inode.c | 2 +-
> > fs/xfs/xfs_iops.c | 15 ++++++++++++---
> > 4 files changed, 15 insertions(+), 6 deletions(-)
> >
> > diff --git a/fs/xfs/libxfs/xfs_trans_inode.c b/fs/xfs/libxfs/xfs_trans_inode.c
> > index 8b5547073379..9ad7c229c617 100644
> > --- a/fs/xfs/libxfs/xfs_trans_inode.c
> > +++ b/fs/xfs/libxfs/xfs_trans_inode.c
> > @@ -63,7 +63,7 @@ xfs_trans_ichgtime(
> > ASSERT(tp);
> > ASSERT(xfs_isilocked(ip, XFS_ILOCK_EXCL));
> >
> > - tv = current_time(inode);
> > + tv = current_cmtime(inode);
> >
> > if (flags & XFS_ICHGTIME_MOD)
> > inode->i_mtime = tv;
> > diff --git a/fs/xfs/xfs_acl.c b/fs/xfs/xfs_acl.c
> > index 791db7d9c849..461adc58cf8c 100644
> > --- a/fs/xfs/xfs_acl.c
> > +++ b/fs/xfs/xfs_acl.c
> > @@ -233,7 +233,7 @@ xfs_acl_set_mode(
> > xfs_ilock(ip, XFS_ILOCK_EXCL);
> > xfs_trans_ijoin(tp, ip, XFS_ILOCK_EXCL);
> > inode->i_mode = mode;
> > - inode->i_ctime = current_time(inode);
> > + inode->i_ctime = current_cmtime(inode);
>
> Hmm, now we're adding a spinlock to all these updates.
> Does lockdep have anything exciting to say about this?
>
> (I don't think it will, just wondering aloud...)
>
I haven't seen anything, but I haven't done any extensive testing yet
either. Still, that might be a good reason to avoid locking in this
scheme if we can.
> > xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> >
> > if (xfs_has_wsync(mp))
> > diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> > index 5808abab786c..80f9d731e261 100644
> > --- a/fs/xfs/xfs_inode.c
> > +++ b/fs/xfs/xfs_inode.c
> > @@ -843,7 +843,7 @@ xfs_init_new_inode(
> > ip->i_df.if_nextents = 0;
> > ASSERT(ip->i_nblocks == 0);
> >
> > - tv = current_time(inode);
> > + tv = current_cmtime(inode);
> > inode->i_mtime = tv;
> > inode->i_atime = tv;
> > inode->i_ctime = tv;
> > diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> > index 24718adb3c16..a0b07f90e16c 100644
> > --- a/fs/xfs/xfs_iops.c
> > +++ b/fs/xfs/xfs_iops.c
> > @@ -565,6 +565,15 @@ xfs_vn_getattr(
> > if (xfs_is_shutdown(mp))
> > return -EIO;
> >
> > + /*
> > + * XFS uses the i_version infrastructure to track any change to
> > + * the inode, including atime updates. This means that the i_version
> > + * returned by getattr doesn't conform to what the callers expect.
> > + * Clear it here so that nfsd will fake up a change cookie from the
> > + * ctime instead.
> > + */
> > + stat->result_mask &= ~STATX_CHANGE_COOKIE;
> > +
> > stat->size = XFS_ISIZE(ip);
> > stat->dev = inode->i_sb->s_dev;
> > stat->mode = inode->i_mode;
> > @@ -573,8 +582,8 @@ xfs_vn_getattr(
> > stat->gid = vfsgid_into_kgid(vfsgid);
> > stat->ino = ip->i_ino;
> > stat->atime = inode->i_atime;
> > - stat->mtime = inode->i_mtime;
> > - stat->ctime = inode->i_ctime;
> > + if (request_mask & (STATX_CTIME|STATX_MTIME))
> > + fill_cmtime_and_mark(inode, stat);
>
> Should we be setting STATX_[CM]TIME in the result_mask, just in case the
> caller asked for ctime and not mtime?
>
>
We already set the result_mask in vfs_getattr_nosec:
stat->result_mask |= STATX_BASIC_STATS;
...and it's OK to return more attrs than were requested.
The bigger issue here is that it's not setting the ctime and mtime
fields while leaving the STATX_CTIME and STATX_MTIME flags set. I'll
plan to fix that up in some fashion in the next post.
Thanks!
> > stat->blocks = XFS_FSB_TO_BB(mp, ip->i_nblocks + ip->i_delayed_blks);
> >
> > if (xfs_has_v3inodes(mp)) {
> > @@ -917,7 +926,7 @@ xfs_setattr_size(
> > if (newsize != oldsize &&
> > !(iattr->ia_valid & (ATTR_CTIME | ATTR_MTIME))) {
> > iattr->ia_ctime = iattr->ia_mtime =
> > - current_time(inode);
> > + current_cmtime(inode);
> > iattr->ia_valid |= ATTR_CTIME | ATTR_MTIME;
> > }
> >
> > --
> > 2.39.2
> >
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-04-11 15:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 14:36 [RFC PATCH 0/3][RESEND] fs: opportunistic high-res file timestamps Jeff Layton
2023-04-11 14:37 ` [RFC PATCH 1/3][RESEND] fs: add infrastructure for opportunistic high-res ctime/mtime updates Jeff Layton
2023-04-11 14:42 ` Darrick J. Wong
2023-04-11 14:54 ` Jeff Layton
2023-04-11 15:07 ` Christian Brauner
2023-04-11 16:04 ` Jeff Layton
2023-04-21 10:23 ` Jan Kara
2023-04-11 14:37 ` [RFC PATCH 2/3][RESEND] shmem: mark for high-res timestamps on next update after getattr Jeff Layton
2023-04-24 7:20 ` kernel test robot
2023-04-11 14:37 ` [RFC PATCH 3/3][RESEND] xfs: mark the inode for high-res timestamp update in getattr Jeff Layton
2023-04-11 14:54 ` Darrick J. Wong
2023-04-11 15:15 ` Christian Brauner
2023-04-11 16:05 ` Jeff Layton
2023-04-11 15:58 ` Jeff Layton [this message]
2023-04-21 2:04 ` kernel test robot
2023-04-11 23:13 ` [RFC PATCH 0/3][RESEND] fs: opportunistic high-res file timestamps Dave Chinner
2023-04-15 11:35 ` Amir Goldstein
2023-04-15 12:13 ` Jeff Layton
2023-04-15 16:19 ` [RFC PATCH 0/3][RESEND] " Chuck Lever III
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=75eebb5ddf9bd21df2782a87208dee2cda7e93e3.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hughd@google.com \
--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-xfs@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.