public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Olga Kornievskaia <okorniev@redhat.com>, chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org, neilb@brown.name, Dai.Ngo@oracle.com,
	 tom@talpey.com
Subject: Re: [PATCH 0/3] nfsd update mtime/ctime on CLONE/COPY with delegated attritutes
Date: Wed, 08 Apr 2026 07:17:08 -0400	[thread overview]
Message-ID: <fc8049617da1b2920144ae27ef0ec71d9deb2e5c.camel@kernel.org> (raw)
In-Reply-To: <20260407235038.55749-1-okorniev@redhat.com>

On Tue, 2026-04-07 at 19:50 -0400, Olga Kornievskaia wrote:
> generic/407 is failing in presence of delegated attributes and this patch series 
> explores the solution where the CLONE compound returns updated mtime/ctime
> in the GETATTR op in the compound.
> 
> It's broken into several pieces as I consider asynchronous copy update the trickest
> because the copy thread currently have no dentry to call notify_change() on. And
> if we are going to keep a copy of it while the copy is running we probably need to
> take a reference on it (which I attempt to do).
> 
> An outstanding question I have is whether or not a CLONE/COPY operation is supposed to
> also update the atime on the source file? But also atime for the dest file as well?
> I'm updating both ctime and mtime for the destination (though Jeff only suggested
> mtime and perhaps I'm missing something in updating ctime as well but I thought it 
> was appropriate). 
> 
> COPY was tested by modifying the linux client to send a GETATTR in the COPY compound.
> Whether or not the client should add the GETATTR to the COPY compound is yet another
> question I have but I guess it would be for Trond.
> 
> Olga Kornievskaia (3):
>   nfsd: update mtime/ctime on CLONE in presense of delegated attributes
>   nfsd: update mtime/ctime on synchronous COPY with delegated attributes
>   nfsd: update mtime/ctime on asynchronous COPY with delegated
>     attributes
> 
>  fs/nfsd/nfs4proc.c | 38 +++++++++++++++++++++++++++++++++++++-
>  fs/nfsd/xdr4.h     |  1 +
>  2 files changed, 38 insertions(+), 1 deletion(-)

This all looks good to me. Thanks for fixing this up, Olga!

Reviewed-by: Jeff Layton <jlayton@kernel.org>

      parent reply	other threads:[~2026-04-08 11:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 23:50 [PATCH 0/3] nfsd update mtime/ctime on CLONE/COPY with delegated attritutes Olga Kornievskaia
2026-04-07 23:50 ` [PATCH 1/3] nfsd: update mtime/ctime on CLONE in presense of delegated attributes Olga Kornievskaia
2026-04-08 13:53   ` Chuck Lever
2026-04-08 15:08     ` Olga Kornievskaia
2026-04-07 23:50 ` [PATCH 2/3] nfsd: update mtime/ctime on synchronous COPY with " Olga Kornievskaia
2026-04-08 13:54   ` Chuck Lever
2026-04-08 15:24     ` Olga Kornievskaia
2026-04-08 16:49       ` Chuck Lever
2026-04-07 23:50 ` [PATCH 3/3] nfsd: update mtime/ctime on asynchronous " Olga Kornievskaia
2026-04-08 14:05   ` Chuck Lever
2026-04-08 15:43     ` Olga Kornievskaia
2026-04-08 11:13 ` [PATCH 0/3] nfsd update mtime/ctime on CLONE/COPY with delegated attritutes Jeff Layton
2026-04-08 11:17 ` Jeff Layton [this message]

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=fc8049617da1b2920144ae27ef0ec71d9deb2e5c.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@brown.name \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.com \
    /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