From: Jeff Layton <jlayton@kernel.org>
To: tavianator@tavianator.com, linux-nfs@vger.kernel.org
Cc: Chuck Lever <chuck.lever@oracle.com>,
Ondrej Valousek <ondrej.valousek.xm@renesas.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/nfsd: Fix creation time serialization order
Date: Tue, 27 Jun 2023 12:09:20 -0400 [thread overview]
Message-ID: <a640835f172acabfc24b10f526d5186b3f98621f.camel@kernel.org> (raw)
In-Reply-To: <4154eb6503988c2096f5d30af26d06863fb5d973.1687554467.git.tavianator@tavianator.com>
On Fri, 2023-06-23 at 17:09 -0400, tavianator@tavianator.com wrote:
> From: Tavian Barnes <tavianator@tavianator.com>
>
> In nfsd4_encode_fattr(), TIME_CREATE was being written out after all
> other times. However, they should be written out in an order that
> matches the bit flags in bmval1, which in this case are
>
> #define FATTR4_WORD1_TIME_ACCESS (1UL << 15)
> #define FATTR4_WORD1_TIME_CREATE (1UL << 18)
> #define FATTR4_WORD1_TIME_DELTA (1UL << 19)
> #define FATTR4_WORD1_TIME_METADATA (1UL << 20)
> #define FATTR4_WORD1_TIME_MODIFY (1UL << 21)
>
> so TIME_CREATE should come second.
>
> I noticed this on a FreeBSD NFSv4.2 client, which supports creation
> times. On this client, file times were weirdly permuted. With this
> patch applied on the server, times looked normal on the client.
>
> Fixes: e377a3e698fb ("nfsd: Add support for the birth time attribute")
> Link: https://unix.stackexchange.com/q/749605/56202
> Signed-off-by: Tavian Barnes <tavianator@tavianator.com>
> ---
> fs/nfsd/nfs4xdr.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
> index 76db2fe29624..3037c5b0623e 100644
> --- a/fs/nfsd/nfs4xdr.c
> +++ b/fs/nfsd/nfs4xdr.c
> @@ -3354,6 +3354,13 @@ nfsd4_encode_fattr(struct xdr_stream *xdr, struct svc_fh *fhp,
> p = xdr_encode_hyper(p, (s64)stat.atime.tv_sec);
> *p++ = cpu_to_be32(stat.atime.tv_nsec);
> }
> + if (bmval1 & FATTR4_WORD1_TIME_CREATE) {
> + p = xdr_reserve_space(xdr, 12);
> + if (!p)
> + goto out_resource;
> + p = xdr_encode_hyper(p, (s64)stat.btime.tv_sec);
> + *p++ = cpu_to_be32(stat.btime.tv_nsec);
> + }
> if (bmval1 & FATTR4_WORD1_TIME_DELTA) {
> p = xdr_reserve_space(xdr, 12);
> if (!p)
> @@ -3374,13 +3381,6 @@ nfsd4_encode_fattr(struct xdr_stream *xdr, struct svc_fh *fhp,
> p = xdr_encode_hyper(p, (s64)stat.mtime.tv_sec);
> *p++ = cpu_to_be32(stat.mtime.tv_nsec);
> }
> - if (bmval1 & FATTR4_WORD1_TIME_CREATE) {
> - p = xdr_reserve_space(xdr, 12);
> - if (!p)
> - goto out_resource;
> - p = xdr_encode_hyper(p, (s64)stat.btime.tv_sec);
> - *p++ = cpu_to_be32(stat.btime.tv_nsec);
> - }
> if (bmval1 & FATTR4_WORD1_MOUNTED_ON_FILEID) {
> u64 ino = stat.ino;
>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2023-06-27 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 21:09 tavianator
2023-06-23 21:48 ` Chuck Lever
2023-06-23 22:05 ` Tavian Barnes
2023-06-27 16:09 ` 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=a640835f172acabfc24b10f526d5186b3f98621f.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ondrej.valousek.xm@renesas.com \
--cc=tavianator@tavianator.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
all inboxes | Powered by JetHome®