From: Chuck Lever <cel@kernel.org>
To: jlayton@kernel.org, Olga Kornievskaia <okorniev@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org, neilb@brown.name, Dai.Ngo@oracle.com,
tom@talpey.com
Subject: Re: [PATCH v4 0/2] nfsd update mtime/ctime on CLONE/COPY with delegated attritutes
Date: Fri, 10 Apr 2026 16:19:29 -0400 [thread overview]
Message-ID: <177585235184.1992986.5886959705627774468.b4-ty@b4> (raw)
In-Reply-To: <20260410160920.56855-1-okorniev@redhat.com>
From: Chuck Lever <chuck.lever@oracle.com>
On Fri, 10 Apr 2026 12:09:18 -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.
>
> Both CLONE and COPY need to update destination file mtime/ctime
> (in presence of delegated timestamp) when file was modified.
>
> [...]
Applied to nfsd-testing, thanks!
[1/2] nfsd: update mtime/ctime on CLONE in presense of delegated attributes
commit: a7f570141bae209189f05fdff295f67fe84dd183
[2/2] nfsd: update mtime/ctime on COPY in presence of delegated attributes
commit: d0814470307048890b3cf6c8b373815f0b8cd64d
--
Chuck Lever
prev parent reply other threads:[~2026-04-10 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 16:09 [PATCH v4 0/2] nfsd update mtime/ctime on CLONE/COPY with delegated attritutes Olga Kornievskaia
2026-04-10 16:09 ` [PATCH v4 1/2] nfsd: update mtime/ctime on CLONE in presense of delegated attributes Olga Kornievskaia
2026-04-10 16:09 ` [PATCH v4 2/2] nfsd: update mtime/ctime on COPY in presence " Olga Kornievskaia
2026-04-10 20:19 ` Chuck Lever [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=177585235184.1992986.5886959705627774468.b4-ty@b4 \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).