mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Trond Myklebust <trondmy@kernel.org>, Anna Schumaker <anna@kernel.org>
Cc: Olga Kornievskaia <aglo@umich.edu>,
	linux-nfs@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] nfs: fix utimensat() for atime with delegated timestamps
Date: Wed, 25 Mar 2026 08:30:06 -0400	[thread overview]
Message-ID: <c36648f66b6e66f8aa555528c8969b1350c3a36f.camel@kernel.org> (raw)
In-Reply-To: <20260324-nfs-7-1-v2-1-d110da3c0036@kernel.org>

On Tue, 2026-03-24 at 13:32 -0400, Jeff Layton wrote:
> xfstest generic/221 is failing with delegated timestamps enabled.  When
> the client holds a WRITE_ATTRS_DELEG delegation, and a userland process
> does a utimensat() for only the atime, the ctime is not properly
> updated. The problem is that the client tries to cache the atime update,
> but there is no mtime update, so the delegated attribute update never
> updates the ctime.
> 
> Delegated timestamps don't have a mechanism to update the ctime in
> accordance with atime-only changes due to utimensat() and the like.
> Change the client to issue an RPC in this case, so that the ctime gets
> properly updated alongside the atime.
> 
> Fixes: 40f45ab3814f ("NFS: Further fixes to attribute delegation a/mtime changes")
> Reported-by: Olga Kornievskaia <aglo@umich.edu>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
>  fs/nfs/inode.c | 9 +--------
>  1 file changed, 1 insertion(+), 8 deletions(-)
> 
> diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
> index 4786343eeee0f874aa1f31ace2f35fdcb83fc7a6..3a5bba7e3c92d4d4fcd65234cd2f10e56f78dee0 100644
> --- a/fs/nfs/inode.c
> +++ b/fs/nfs/inode.c
> @@ -757,14 +757,7 @@ nfs_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
>  	} else if (nfs_have_delegated_atime(inode) &&
>  		   attr->ia_valid & ATTR_ATIME &&
>  		   !(attr->ia_valid & ATTR_MTIME)) {
> -		if (attr->ia_valid & ATTR_ATIME_SET) {
> -			if (uid_eq(task_uid, owner_uid)) {
> -				spin_lock(&inode->i_lock);
> -				nfs_set_timestamps_to_ts(inode, attr);
> -				spin_unlock(&inode->i_lock);
> -				attr->ia_valid &= ~(ATTR_ATIME|ATTR_ATIME_SET);
> -			}
> -		} else {

This probably deserves a comment. How about something like:

		/*
		 * An atime-only update via an explicit setattr (e.g.: utimensat() and
		 * the like) requires updating the ctime as well. Delegated timestamps
		 * don't have a mechanism for updating the ctime with a delegated
		 * atime-only update, so an RPC must be issued.
		 */

> +		if (!(attr->ia_valid & ATTR_ATIME_SET)) {
>  			nfs_update_delegated_atime(inode);
>  			attr->ia_valid &= ~ATTR_ATIME;
>  		}

-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2026-03-25 12:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 17:32 [PATCH v2 0/2] nfs: delegated attribute fixes Jeff Layton
2026-03-24 17:32 ` [PATCH v2 1/2] nfs: fix utimensat() for atime with delegated timestamps Jeff Layton
2026-03-25 12:30   ` Jeff Layton [this message]
2026-04-07 13:28     ` Olga Kornievskaia
2026-04-07 21:24       ` Olga Kornievskaia
2026-03-24 17:32 ` [PATCH v2 2/2] nfs: update inode ctime after removexattr operation Jeff Layton
2026-03-27 15:11   ` Olga Kornievskaia
2026-03-27 15:50     ` Jeff Layton
2026-03-27 16:20       ` Olga Kornievskaia
2026-03-27 16:59         ` Jeff Layton
2026-03-27 18:22           ` Thomas Haynes
2026-03-27 19:36             ` Olga Kornievskaia
2026-03-27 20:02               ` Thomas Haynes
2026-03-31 18:17                 ` Olga Kornievskaia
2026-03-31 18:50                   ` Thomas Haynes
2026-03-31 21:10                     ` Olga Kornievskaia
2026-03-31 22:57                   ` Rick Macklem
2026-03-31 11:42             ` Jeff Layton
2026-03-31 18:47               ` Thomas Haynes
2026-03-31 21:19                 ` Jeff Layton
2026-03-31 22:16                   ` Thomas Haynes
2026-03-31 22:36                     ` 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=c36648f66b6e66f8aa555528c8969b1350c3a36f.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=aglo@umich.edu \
    --cc=anna@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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