public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: Jianglei Nie <niejianglei2021@163.com>,
	jgg@ziepe.ca, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/hfi1: fix potential memory leak in setup_base_ctxt()
Date: Mon, 18 Jul 2022 15:30:43 +0300	[thread overview]
Message-ID: <YtVSc7aazgxVFHRa@unreal> (raw)
In-Reply-To: <be437471-0080-8e9c-978a-6029c7826335@cornelisnetworks.com>

On Mon, Jul 18, 2022 at 08:11:59AM -0400, Dennis Dalessandro wrote:
> On 7/18/22 6:39 AM, Leon Romanovsky wrote:
> > On Mon, Jul 11, 2022 at 07:52:25AM -0400, Dennis Dalessandro wrote:
> >> On 7/11/22 3:07 AM, Jianglei Nie wrote:
> >>> setup_base_ctxt() allocates a memory chunk for uctxt->groups with
> >>> hfi1_alloc_ctxt_rcv_groups(). When init_user_ctxt() fails, uctxt->groups
> >>> is not released, which will lead to a memory leak.
> >>>
> >>> We should release the uctxt->groups with hfi1_free_ctxt_rcv_groups()
> >>> when init_user_ctxt() fails.
> >>>
> >>> Signed-off-by: Jianglei Nie <niejianglei2021@163.com>
> >>> ---
> >>>  drivers/infiniband/hw/hfi1/file_ops.c | 4 +++-
> >>>  1 file changed, 3 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/infiniband/hw/hfi1/file_ops.c b/drivers/infiniband/hw/hfi1/file_ops.c
> >>> index 2e4cf2b11653..629beff053ad 100644
> >>> --- a/drivers/infiniband/hw/hfi1/file_ops.c
> >>> +++ b/drivers/infiniband/hw/hfi1/file_ops.c
> >>> @@ -1179,8 +1179,10 @@ static int setup_base_ctxt(struct hfi1_filedata *fd,
> >>>  		goto done;
> >>>  
> >>>  	ret = init_user_ctxt(fd, uctxt);
> >>> -	if (ret)
> >>> +	if (ret) {
> >>> +		hfi1_free_ctxt_rcv_groups(uctxt);
> >>>  		goto done;
> >>> +	}
> >>>  
> >>>  	user_init(uctxt);
> >>>  
> >>
> >> Doesn't seem like this patch is correct. The free is done when the file is
> >> closed, along with other clean up stuff. See hfi1_file_close().
> > 
> > Can setup_base_ctxt() be called twice for same uctxt?
> > You are allocating rcd->groups and not releasing.
> 
> The first thing assign_ctxt() does is a check of the fd->uctxt and it bails with
> -EINVAL. So effectively only once.

I'm slightly confused. How will you release rcd->groups?

assign_ctxt()
 -> setup_base_ctxt()
   -> hfi1_alloc_ctxt_rcv_groups()
      ,,,
      rcd->groups = kzalloc...
      ...
   -> init_user_ctxt() <-- fails and leaves fd->uctx == NULL


...
hfi1_file_close()
  struct hfi1_ctxtdata *uctxt = fdata->uctxt;
  ...
  if (!uctxt)             <-- This is our case
     goto done; 
  ...

done:
  if (refcount_dec_and_test(&dd->user_refcount))
     complete(&dd->user_comp);

  cleanup_srcu_struct(&fdata->pq_srcu);
  kfree(fdata);
  return 0;



> 
> -Denny
> 
> 

  reply	other threads:[~2022-07-18 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  7:07 [PATCH] RDMA/hfi1: fix potential memory leak in setup_base_ctxt() Jianglei Nie
2022-07-11 11:52 ` Dennis Dalessandro
2022-07-18 10:39   ` Leon Romanovsky
2022-07-18 12:11     ` Dennis Dalessandro
2022-07-18 12:30       ` Leon Romanovsky [this message]
2022-07-18 13:56         ` Dennis Dalessandro
2022-07-19  5:26           ` Leon Romanovsky

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=YtVSc7aazgxVFHRa@unreal \
    --to=leon@kernel.org \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=niejianglei2021@163.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