From: Jeff Layton <jlayton@kernel.org>
To: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>, NeilBrown <neilb@suse.de>
Cc: stable@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org, Boyang Xue <bxue@redhat.com>
Subject: Re: [PATCH] nfs: don't report STATX_BTIME in ->getattr
Date: Mon, 12 Jun 2023 09:39:29 -0400 [thread overview]
Message-ID: <5cc527156b186ec0f57ebd82874cc6eda2866c92.camel@kernel.org> (raw)
In-Reply-To: <20230612133404.181166-1-jlayton@kernel.org>
On Mon, 2023-06-12 at 09:34 -0400, Jeff Layton wrote:
> NFS doesn't properly support reporting the btime in getattr (yet), but
> 61a968b4f05e mistakenly added it to the request_mask. This causes statx
> for STATX_BTIME to report a zeroed out btime instead of properly
> clearing the flag.
>
> Cc: stable@vger.kernel.org # v6.3+
> Fixes: 61a968b4f05e ("nfs: report the inode version in getattr if requested")
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Trond/Anna,
If this patch looks OK, could you also add these tags to the commit log?
Link: https://bugzilla.redhat.com/show_bug.cgi?id=2214134
Reported-by: Boyang Xue <bxue@redhat.com>
I forgot to tack them on before sending.
Thanks!
> ---
> fs/nfs/inode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
> index bc4cac08bb24..9b51ffd7281d 100644
> --- a/fs/nfs/inode.c
> +++ b/fs/nfs/inode.c
> @@ -846,7 +846,7 @@ int nfs_getattr(struct mnt_idmap *idmap, const struct path *path,
>
> request_mask &= STATX_TYPE | STATX_MODE | STATX_NLINK | STATX_UID |
> STATX_GID | STATX_ATIME | STATX_MTIME | STATX_CTIME |
> - STATX_INO | STATX_SIZE | STATX_BLOCKS | STATX_BTIME |
> + STATX_INO | STATX_SIZE | STATX_BLOCKS |
> STATX_CHANGE_COOKIE;
>
> if ((query_flags & AT_STATX_DONT_SYNC) && !force_sync) {
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2023-06-12 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 13:34 Jeff Layton
2023-06-12 13:39 ` 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=5cc527156b186ec0f57ebd82874cc6eda2866c92.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=anna@kernel.org \
--cc=bxue@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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®