From: Praveen Kannoju <praveen.kannoju@oracle.com>
To: Leon Romanovsky <leon@kernel.org>,
"yishaih@nvidia.com" <yishaih@nvidia.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Anand Khoje <anand.a.khoje@oracle.com>,
Manjunath Patil <manjunath.b.patil@oracle.com>
Subject: RE: [PATCH v4] IB/mlx4: Fix stale CM id_map entries when RTU is never received
Date: Thu, 16 Jul 2026 08:33:38 +0000 [thread overview]
Message-ID: <BL0PR10MB282081675D85A0852A82FF198CC72@BL0PR10MB2820.namprd10.prod.outlook.com> (raw)
In-Reply-To: <178419059769.297515.12559710952711271768.b4-ty@kernel.org>
Oracle Confidential
Thank you very much, Leon.
-
Praveen.
Oracle Confidential
> -----Original Message-----
> From: Leon Romanovsky <leon@kernel.org>
> Sent: Thursday, July 16, 2026 2:00 PM
> To: yishaih@nvidia.com; jgg@ziepe.ca; linux-rdma@vger.kernel.org; linux-
> kernel@vger.kernel.org; Praveen Kannoju <praveen.kannoju@oracle.com>
> Subject: Re: [PATCH v4] IB/mlx4: Fix stale CM id_map entries when RTU is
> never received
>
>
> On Wed, 15 Jul 2026 08:07:38 +0000, Praveen Kumar Kannoju wrote:
> > mlx4_ib_multiplex_cm_handler() allocates an id_map_entry for CM
> > transactions, but the entry is normally released only on DREQ or REJ
> > flows.
> >
> > In the duplicate REP handling scenario, cm_dup_rep_handler() may be
> > invoked when the remote side receives a REP for which no matching
> > cm_id_priv exists. In such cases the CM handshake never reaches RTU,
> > and the sender side may never receive either DREQ or REJ cleanup events.
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] IB/mlx4: Fix stale CM id_map entries when RTU is never received
> https://git.kernel.org/rdma/rdma/c/548897f0f78837
>
> Best regards,
> --
> Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-07-16 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:07 Praveen Kumar Kannoju
2026-07-16 8:29 ` Leon Romanovsky
2026-07-16 8:33 ` Praveen Kannoju [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=BL0PR10MB282081675D85A0852A82FF198CC72@BL0PR10MB2820.namprd10.prod.outlook.com \
--to=praveen.kannoju@oracle.com \
--cc=anand.a.khoje@oracle.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=manjunath.b.patil@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox