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 1/1] NFSD: fix setting FMODE_NOCMTIME in nfs4_open_delegation
Date: Fri, 19 Dec 2025 13:04:32 -0500 [thread overview]
Message-ID: <6bf3bc04e3dd962b9d8f93b994e893caf59741d4.camel@kernel.org> (raw)
In-Reply-To: <20251219175955.4480-1-okorniev@redhat.com>
On Fri, 2025-12-19 at 12:59 -0500, Olga Kornievskaia wrote:
> fstests generic/215 and generic/407 were failing because the server
> wasn't updating mtime properly. When deleg attribute support is not
> compiled in and thus no attribute delegation was given, the server
> was skipping updating mtime and ctime because FMODE_NOCMTIME was
> uncoditionally set for the write delegation.
>
> Fixes: e5e9b24ab8fa ("nfsd: freeze c/mtime updates with outstanding WRITE_ATTRS delegation")
> Signed-off-by: Olga Kornievskaia <okorniev@redhat.com>
> ---
> fs/nfsd/nfs4state.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 808c24fb5c9a..d64650c47f79 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -6327,7 +6327,8 @@ nfs4_open_delegation(struct svc_rqst *rqstp, struct nfsd4_open *open,
> dp->dl_ctime = stat.ctime;
> dp->dl_mtime = stat.mtime;
> spin_lock(&f->f_lock);
> - f->f_mode |= FMODE_NOCMTIME;
> + if (deleg_ts)
> + f->f_mode |= FMODE_NOCMTIME;
> spin_unlock(&f->f_lock);
> trace_nfsd_deleg_write(&dp->dl_stid.sc_stateid);
> } else {
Nice catch.
We only want to disable c/mtime updates in the case where timestamps
are delegated. In the non-delegated case, they need to be updated with
every write. This seems correct to me.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-12-19 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 17:59 [PATCH 1/1] NFSD: fix setting FMODE_NOCMTIME in nfs4_open_delegation Olga Kornievskaia
2025-12-19 18:04 ` Jeff Layton [this message]
2025-12-19 19:21 ` Chuck Lever
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=6bf3bc04e3dd962b9d8f93b994e893caf59741d4.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 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.