public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: dai.ngo@oracle.com
Cc: Olga Kornievskaia <aglo@umich.edu>,
	linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] NFSD: Fix use-after-free warning when doing inter-server copy
Date: Fri, 19 Feb 2021 22:20:57 -0500	[thread overview]
Message-ID: <20210220032057.GA25183@fieldses.org> (raw)
In-Reply-To: <69ea46ff-80d1-acfa-22a5-3d1b6230728f@oracle.com>

On Fri, Feb 19, 2021 at 05:31:58PM -0800, dai.ngo@oracle.com wrote:
> If this is the cause why we don't drop the mount after the copy
> then I can restore the patch and look into this problem. Unfortunately,
> all my test machines are down for maintenance until Sunday/Monday.

I think we can take some time to figure out what's actually going on
here before reverting anything.

--b.

> 
> -Dai
> 
> On 2/19/21 5:09 PM, J. Bruce Fields wrote:
> >Dai, do you have a copy of the original use-after-free warning?
> >
> >--b.
> >
> >On Fri, Feb 19, 2021 at 07:18:53PM -0500, Olga Kornievskaia wrote:
> >>Hi Dai (Bruce),
> >>
> >>This patch is what broke the mount that's now left behind between the
> >>source server and the destination server. We are no longer dropping
> >>the necessary reference on the mount to go away. I haven't been paying
> >>as much attention as I should have been to the changes. The original
> >>code called fput(src) so a simple refcount of the file. Then things
> >>got complicated and moved to nfsd_file_put(). So I don't understand
> >>complexity. But we need to do some kind of put to decrement the needed
> >>reference on the superblock. Bruce any ideas? Can we go back to
> >>fput()?
> >>
> >>On Thu, Oct 29, 2020 at 3:08 PM Dai Ngo <dai.ngo@oracle.com> wrote:
> >>>The source file nfsd_file is not constructed the same as other
> >>>nfsd_file's via nfsd_file_alloc. nfsd_file_put should not be
> >>>called to free the object; nfsd_file_put is not the inverse of
> >>>kzalloc, instead kfree is called by nfsd4_do_async_copy when done.
> >>>
> >>>Fixes: ce0887ac96d3 ("NFSD add nfs4 inter ssc to nfsd4_copy")
> >>>Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
> >>>---
> >>>  fs/nfsd/nfs4proc.c | 2 +-
> >>>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>>diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> >>>index ad2fa1a8e7ad..9c43cad7e408 100644
> >>>--- a/fs/nfsd/nfs4proc.c
> >>>+++ b/fs/nfsd/nfs4proc.c
> >>>@@ -1299,7 +1299,7 @@ nfsd4_cleanup_inter_ssc(struct vfsmount *ss_mnt, struct nfsd_file *src,
> >>>                         struct nfsd_file *dst)
> >>>  {
> >>>         nfs42_ssc_close(src->nf_file);
> >>>-       nfsd_file_put(src);
> >>>+       /* 'src' is freed by nfsd4_do_async_copy */
> >>>         nfsd_file_put(dst);
> >>>         mntput(ss_mnt);
> >>>  }
> >>>--
> >>>2.20.1.1226.g1595ea5.dirty
> >>>

  reply	other threads:[~2021-02-20  3:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 19:07 [PATCH 0/2] NFSD: Fix use-after-free warning when doing inter-server copy Dai Ngo
2020-10-29 19:07 ` [PATCH 1/2] " Dai Ngo
2021-02-20  0:18   ` Olga Kornievskaia
2021-02-20  1:09     ` J. Bruce Fields
2021-02-20  1:15       ` dai.ngo
2021-02-20  1:31       ` dai.ngo
2021-02-20  3:20         ` J. Bruce Fields [this message]
2021-02-20  3:41           ` dai.ngo
2021-02-20 14:08           ` Olga Kornievskaia
2021-02-21  4:16             ` dai.ngo
2021-02-22 18:34               ` dai.ngo
2021-02-22 21:46                 ` dai.ngo
2021-02-22 22:01                   ` dai.ngo
2021-02-22 22:08                     ` dai.ngo
2021-02-24 22:35                       ` Olga Kornievskaia
2021-02-25  2:26                         ` dai.ngo
2021-02-25 18:58                           ` dai.ngo
2021-03-01 18:15                             ` Chuck Lever
2020-10-29 19:07 ` [PATCH 2/2] NFSD: fix missing refcount in nfsd4_copy by nfsd4_do_async_copy Dai Ngo
2020-11-05 22:25 ` [PATCH 0/2] NFSD: Fix use-after-free warning when doing inter-server copy J. Bruce Fields

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=20210220032057.GA25183@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=aglo@umich.edu \
    --cc=dai.ngo@oracle.com \
    --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