[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <175259401527.1095462.15384402941904177297.b4-ty@oracle.com>
Date: Tue, 15 Jul 2025 11:42:02 -0400
From: Chuck Lever <cel@...nel.org>
To: NeilBrown <neil@...wn.name>,
Olga Kornievskaia <okorniev@...hat.com>,
Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>,
Jeff Layton <jlayton@...nel.org>
Cc: Chuck Lever <chuck.lever@...cle.com>,
linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nfsd: don't set the ctime on delegated atime updates
From: Chuck Lever <chuck.lever@...cle.com>
On Tue, 15 Jul 2025 07:34:10 -0400, Jeff Layton wrote:
> Clients will typically precede a DELEGRETURN for a delegation with
> delegated timestamp with a SETATTR to set the timestamps on the server
> to match what the client has.
>
> knfsd implements this by using the nfsd_setattr() infrastructure, which
> will set ATTR_CTIME on any update that goes to notify_change(). This is
> problematic as it means that the client will get a spurious ctime
> updates when updating the atime.
>
> [...]
Applied to nfsd-testing, thanks!
Because this patch touches generic attribute handling, I'm targeting
it for v6.18.
[1/1] nfsd: don't set the ctime on delegated atime updates
commit: aaf2b07a551950a6e4deab07f6cf73c4a6592a35
--
Chuck Lever
Powered by blists - more mailing lists