From: Chuck Lever III <chuck.lever@oracle.com>
To: Dai Ngo <dai.ngo@oracle.com>
Cc: "jlayton@kernel.org" <jlayton@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/1] NFSD: fix use-after-free on source server when doing inter-server copy
Date: Mon, 26 Sep 2022 18:43:29 +0000 [thread overview]
Message-ID: <A6371482-E1B0-4F93-B7DD-5EC5B468C67B@oracle.com> (raw)
In-Reply-To: <1664215156-9970-1-git-send-email-dai.ngo@oracle.com>
> On Sep 26, 2022, at 1:59 PM, Dai Ngo <dai.ngo@oracle.com> wrote:
>
> Hi Chuck,
>
> The v3 version simplifies the check for sc_cp_list empty in
> nfs4_free_deleg and nfs4_free_ol_stateid, as Jeff pointed out.
>
> Thanks,
>
> Dai Ngo (1):
> NFSD: fix use-after-free on source server when doing inter-server copy
>
> fs/nfsd/nfs4state.c | 5 +++++
> 1 file changed, 5 insertions(+)
Thanks, Dai. (Re)applied to nfsd's for-next.
--
Chuck Lever
prev parent reply other threads:[~2022-09-26 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 17:59 [PATCH v3 0/1] NFSD: fix use-after-free on source server when doing inter-server copy Dai Ngo
2022-09-26 17:59 ` [PATCH v3 1/1] " Dai Ngo
2022-09-26 18:43 ` Chuck Lever III [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=A6371482-E1B0-4F93-B7DD-5EC5B468C67B@oracle.com \
--to=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.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;
as well as URLs for NNTP newsgroup(s).