From: Leon Romanovsky <leon@kernel.org>
To: Praveen Kumar Kannoju <praveen.kannoju@oracle.com>
Cc: yishaih@nvidia.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, anand.a.khoje@oracle.com,
manjunath.b.patil@oracle.com
Subject: Re: [PATCH] IB/mlx4: delete allocated id_map_entry while sending REJ
Date: Tue, 12 May 2026 15:58:19 +0300 [thread overview]
Message-ID: <20260512125819.GT15586@unreal> (raw)
In-Reply-To: <20260506090824.359239-1-praveen.kannoju@oracle.com>
On Wed, May 06, 2026 at 09:08:24AM +0000, Praveen Kumar Kannoju wrote:
> During scenarios where a REJ is sent after a REQ or REP, the allocated
> is_map_entry remains in memory, resulting in a memory leak. Scheduling the
> entry for deletion during REJ handling, if it is not NULL, resolves the
> issue.
Do you have kmemleak output to prove the leak?
>
> Signed-off-by: Praveen Kumar Kannoju <praveen.kannoju@oracle.com>
> ---
> drivers/infiniband/hw/mlx4/cm.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/infiniband/hw/mlx4/cm.c b/drivers/infiniband/hw/mlx4/cm.c
> index 63a868a3822f..21f2f401ed61 100644
> --- a/drivers/infiniband/hw/mlx4/cm.c
> +++ b/drivers/infiniband/hw/mlx4/cm.c
> @@ -321,10 +321,9 @@ int mlx4_ib_multiplex_cm_handler(struct ib_device *ibdev, int port, int slave_id
> __func__, slave_id, sl_cm_id);
> return PTR_ERR(id);
> }
> - } else if (mad->mad_hdr.attr_id == CM_REJ_ATTR_ID ||
> - mad->mad_hdr.attr_id == CM_SIDR_REP_ATTR_ID) {
> + } else if (mad->mad_hdr.attr_id == CM_SIDR_REP_ATTR_ID)
> return 0;
> - } else {
> + else {
It is now similar to the "if (... && REJ_REASON(mad) == IB_CM_REJ_TIMEOUT)"
for active-side timeout above.
Thanks
> sl_cm_id = get_local_comm_id(mad);
> id = id_map_get(ibdev, &pv_cm_id, slave_id, sl_cm_id);
> }
> @@ -338,7 +337,8 @@ int mlx4_ib_multiplex_cm_handler(struct ib_device *ibdev, int port, int slave_id
> cont:
> set_local_comm_id(mad, id->pv_cm_id);
>
> - if (mad->mad_hdr.attr_id == CM_DREQ_ATTR_ID)
> + if (mad->mad_hdr.attr_id == CM_DREQ_ATTR_ID ||
> + mad->mad_hdr.attr_id == CM_REJ_ATTR_ID)
> schedule_delayed(ibdev, id);
> return 0;
> }
> --
> 2.43.7
>
next prev parent reply other threads:[~2026-05-12 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 9:08 [PATCH] IB/mlx4: delete allocated id_map_entry while sending REJ Praveen Kumar Kannoju
2026-05-12 12:58 ` Leon Romanovsky [this message]
2026-05-13 10:46 ` Praveen Kannoju
2026-06-02 19:07 ` Jason Gunthorpe
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=20260512125819.GT15586@unreal \
--to=leon@kernel.org \
--cc=anand.a.khoje@oracle.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=manjunath.b.patil@oracle.com \
--cc=praveen.kannoju@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.