public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: yishaih@nvidia.com, dledford@redhat.com, jgg@ziepe.ca,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/mlx4: Fix potential memory leak
Date: Sun, 7 Nov 2021 09:40:00 +0200	[thread overview]
Message-ID: <YYeC0O3wL8X0uSsY@unreal> (raw)
In-Reply-To: <1636020852-3951757-1-git-send-email-jiasheng@iscas.ac.cn>

On Thu, Nov 04, 2021 at 10:14:12AM +0000, Jiasheng Jiang wrote:
> In the error path, the dev->dev isn't released.
> Therefore, it might be better to fix it to avoid
> potential memory leak.
> 
> Fixes: 9376932 ("IB/mlx4_ib: Add support for user MR re-registration")
> Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
> ---
>  drivers/infiniband/hw/mlx4/mr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

I don't understand about which release you are talking, but this patch
can't be right. You are supposed to call to "release_mpt_entry" only in
the error flows which after successful mlx4_mr_hw_get_mpt().

Thanks

> 
> diff --git a/drivers/infiniband/hw/mlx4/mr.c b/drivers/infiniband/hw/mlx4/mr.c
> index 50becc0..d8ae92e 100644
> --- a/drivers/infiniband/hw/mlx4/mr.c
> +++ b/drivers/infiniband/hw/mlx4/mr.c
> @@ -473,7 +473,7 @@ struct ib_mr *mlx4_ib_rereg_user_mr(struct ib_mr *mr, int flags, u64 start,
>  	 */
>  	err =  mlx4_mr_hw_get_mpt(dev->dev, &mmr->mmr, &pmpt_entry);
>  	if (err)
> -		return ERR_PTR(err);
> +		goto release_mpt_entry;
>  
>  	if (flags & IB_MR_REREG_PD) {
>  		err = mlx4_mr_hw_change_pd(dev->dev, *pmpt_entry,
> -- 
> 2.7.4
> 

      reply	other threads:[~2021-11-07  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 10:14 [PATCH] RDMA/mlx4: Fix potential memory leak Jiasheng Jiang
2021-11-07  7:40 ` Leon Romanovsky [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=YYeC0O3wL8X0uSsY@unreal \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=jiasheng@iscas.ac.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yishaih@nvidia.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