From: Mark Zhang <markzhang@nvidia.com>
To: Gerd Rausch <gerd.rausch@oracle.com>,
<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH 1/1] RDMA/cma: Fix rdma_resolve_route memory leak
Date: Fri, 25 Jun 2021 13:49:11 +0800 [thread overview]
Message-ID: <27a35a75-813d-ef1e-c9ca-d4ecbc5a95d2@nvidia.com> (raw)
In-Reply-To: <f6662b7b-bdb7-2706-1e12-47c61d3474b6@oracle.com>
On 6/25/2021 2:55 AM, Gerd Rausch wrote:
> Fix a memory leak when "rmda_resolve_route" is called
> more than once on the same "rdma_cm_id".
>
> Signed-off-by: Gerd Rausch <gerd.rausch@oracle.com>
> ---
> drivers/infiniband/core/cma.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/core/cma.c b/drivers/infiniband/core/cma.c
> index ab148a696c0c..4a76d5b4163e 100644
> --- a/drivers/infiniband/core/cma.c
> +++ b/drivers/infiniband/core/cma.c
> @@ -2819,7 +2819,8 @@ static int cma_resolve_ib_route(struct rdma_id_private *id_priv,
>
> cma_init_resolve_route_work(work, id_priv);
>
> - route->path_rec = kmalloc(sizeof *route->path_rec, GFP_KERNEL);
> + if (!route->path_rec)
> + route->path_rec = kmalloc(sizeof *route->path_rec, GFP_KERNEL);
> if (!route->path_rec) {
> ret = -ENOMEM;
> goto err1;
If route->path_rec does exist (meaning this is not the first time
called), then it would be freed if cma_query_ib_route() below is failed,
is it good?
next prev parent reply other threads:[~2021-06-25 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 18:55 [PATCH 1/1] RDMA/cma: Fix rdma_resolve_route memory leak Gerd Rausch
2021-06-25 5:49 ` Mark Zhang [this message]
2021-06-25 8:15 ` Haakon Bugge
2021-06-25 16:27 ` Gerd Rausch
2021-06-25 15:03 ` Jason Gunthorpe
2021-06-25 16:27 ` Gerd Rausch
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=27a35a75-813d-ef1e-c9ca-d4ecbc5a95d2@nvidia.com \
--to=markzhang@nvidia.com \
--cc=dledford@redhat.com \
--cc=gerd.rausch@oracle.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@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