From: Greg KH <greg@kroah.com>
To: Ovidiu Panait <ovidiu.panait@eng.windriver.com>
Cc: stable@vger.kernel.org, Dai Ngo <dai.ngo@oracle.com>,
Xingyuan Mo <hdthky0@gmail.com>,
Chuck Lever <chuck.lever@oracle.com>,
Ovidiu Panait <ovidiu.panait@windriver.com>
Subject: Re: [PATCH 5.15/5.10 1/1] NFSD: fix use-after-free in __nfs42_ssc_open()
Date: Tue, 28 Mar 2023 16:11:42 +0200 [thread overview]
Message-ID: <ZCL1notX-7ICuqDH@kroah.com> (raw)
In-Reply-To: <20230328134759.401789-1-ovidiu.panait@eng.windriver.com>
On Tue, Mar 28, 2023 at 04:47:59PM +0300, Ovidiu Panait wrote:
> From: Dai Ngo <dai.ngo@oracle.com>
>
> commit 75333d48f92256a0dec91dbf07835e804fc411c0 upstream.
>
> Problem caused by source's vfsmount being unmounted but remains
> on the delayed unmount list. This happens when nfs42_ssc_open()
> return errors.
>
> Fixed by removing nfsd4_interssc_connect(), leave the vfsmount
> for the laundromat to unmount when idle time expires.
>
> We don't need to call nfs_do_sb_deactive when nfs42_ssc_open
> return errors since the file was not opened so nfs_server->active
> was not incremented. Same as in nfsd4_copy, if we fail to
> launch nfsd4_do_async_copy thread then there's no need to
> call nfs_do_sb_deactive
>
> Reported-by: Xingyuan Mo <hdthky0@gmail.com>
> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
> Tested-by: Xingyuan Mo <hdthky0@gmail.com>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
> ---
> fs/nfsd/nfs4proc.c | 22 ++++++----------------
> 1 file changed, 6 insertions(+), 16 deletions(-)
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-03-28 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 13:47 [PATCH 5.15/5.10 1/1] NFSD: fix use-after-free in __nfs42_ssc_open() Ovidiu Panait
2023-03-28 14:11 ` Greg KH [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=ZCL1notX-7ICuqDH@kroah.com \
--to=greg@kroah.com \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=hdthky0@gmail.com \
--cc=ovidiu.panait@eng.windriver.com \
--cc=ovidiu.panait@windriver.com \
--cc=stable@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