RE: [PATCH v4] IB/mlx4: Fix stale CM id_map entries when RTU is never received
From: Praveen Kannoju
Date: Thu Jul 16 2026 - 04:34:23 EST
Oracle Confidential
Thank you very much, Leon.
-
Praveen.
Oracle Confidential
+AD4- -----Original Message-----
+AD4- From: Leon Romanovsky +ADw-leon+AEA-kernel.org+AD4-
+AD4- Sent: Thursday, July 16, 2026 2:00 PM
+AD4- To: yishaih+AEA-nvidia.com+ADs- jgg+AEA-ziepe.ca+ADs- linux-rdma+AEA-vger.kernel.org+ADs- linux-
+AD4- kernel+AEA-vger.kernel.org+ADs- Praveen Kannoju +ADw-praveen.kannoju+AEA-oracle.com+AD4-
+AD4- Subject: Re: +AFs-PATCH v4+AF0- IB/mlx4: Fix stale CM id+AF8-map entries when RTU is
+AD4- never received
+AD4-
+AD4-
+AD4- On Wed, 15 Jul 2026 08:07:38 +-0000, Praveen Kumar Kannoju wrote:
+AD4- +AD4- mlx4+AF8-ib+AF8-multiplex+AF8-cm+AF8-handler() allocates an id+AF8-map+AF8-entry for CM
+AD4- +AD4- transactions, but the entry is normally released only on DREQ or REJ
+AD4- +AD4- flows.
+AD4- +AD4-
+AD4- +AD4- In the duplicate REP handling scenario, cm+AF8-dup+AF8-rep+AF8-handler() may be
+AD4- +AD4- invoked when the remote side receives a REP for which no matching
+AD4- +AD4- cm+AF8-id+AF8-priv exists. In such cases the CM handshake never reaches RTU,
+AD4- +AD4- and the sender side may never receive either DREQ or REJ cleanup events.
+AD4- +AD4-
+AD4- +AD4- +AFs-...+AF0-
+AD4-
+AD4- Applied, thanks+ACE-
+AD4-
+AD4- +AFs-1/1+AF0- IB/mlx4: Fix stale CM id+AF8-map entries when RTU is never received
+AD4- https://git.kernel.org/rdma/rdma/c/548897f0f78837
+AD4-
+AD4- Best regards,
+AD4- --
+AD4- Leon Romanovsky +ADw-leon+AEA-kernel.org+AD4-