From: Chuck Lever <chuck.lever@oracle.com>
To: "trondmy@kernel.org" <trondmy@kernel.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Fix NFSv3 SETATTR behaviours
Date: Tue, 20 Feb 2024 10:28:42 -0500 [thread overview]
Message-ID: <ZdTFKg2IB5woA7ql@manet.1015granger.net> (raw)
In-Reply-To: <20240216012451.22725-1-trondmy@kernel.org>
On Thu, Feb 15, 2024 at 08:24:49PM -0500, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> Fix recent regressions in nfsd_setattr(), and fix the "guarded SETATTR"
> behaviour for NFSv3.
>
> Trond Myklebust (2):
> nfsd: Fix a regression in nfsd_setattr()
> nfsd: Fix NFSv3 atomicity bugs in nfsd_setattr()
>
> fs/nfsd/nfs3proc.c | 6 ++++--
> fs/nfsd/nfs3xdr.c | 5 +----
> fs/nfsd/nfs4proc.c | 7 +++++--
> fs/nfsd/nfs4state.c | 2 +-
> fs/nfsd/nfsproc.c | 6 +++---
> fs/nfsd/vfs.c | 29 ++++++++++++++++++++---------
> fs/nfsd/vfs.h | 2 +-
> fs/nfsd/xdr3.h | 2 +-
> 8 files changed, 36 insertions(+), 23 deletions(-)
>
> --
> 2.43.1
>
Both applied to nfsd-next. Thanks gents!
--
Chuck Lever
prev parent reply other threads:[~2024-02-20 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 1:24 [PATCH v2 0/2] Fix NFSv3 SETATTR behaviours trondmy
2024-02-16 1:24 ` [PATCH v2 1/2] nfsd: Fix a regression in nfsd_setattr() trondmy
2024-02-16 1:24 ` [PATCH v2 2/2] nfsd: Fix NFSv3 atomicity bugs " trondmy
2024-02-18 14:24 ` Jeff Layton
2024-02-18 22:01 ` NeilBrown
2024-02-16 13:33 ` [PATCH v2 1/2] nfsd: Fix a regression " Chuck Lever
2024-02-16 18:18 ` Trond Myklebust
2024-02-16 18:19 ` Chuck Lever III
2024-02-16 18:25 ` Chuck Lever III
2024-02-16 18:57 ` Trond Myklebust
2024-02-17 17:05 ` Chuck Lever
2024-02-17 18:16 ` Trond Myklebust
2024-02-18 14:21 ` Jeff Layton
2024-02-18 21:57 ` NeilBrown
2024-02-19 1:33 ` Trond Myklebust
2024-02-20 15:28 ` 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=ZdTFKg2IB5woA7ql@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@kernel.org \
/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