linux-kernel - Re: [PATCH for-next] RDMA/cm: Rate limit destroy CM ID timeout error message

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHYDg1Rd=meRaF=AJAXJ+5_hDaJckaZs7DJUtXAY_D2z_a6wsw@mail.gmail.com>
Date: Tue, 16 Sep 2025 10:36:43 -0400
From: Jacob Moroni <jmoroni@...gle.com>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: Håkon Bugge <haakon.bugge@...cle.com>, 
	Leon Romanovsky <leon@...nel.org>, Sean Hefty <shefty@...dia.com>, 
	Vlad Dumitrescu <vdumitrescu@...dia.com>, Or Har-Toov <ohartoov@...dia.com>, 
	Manjunath Patil <manjunath.b.patil@...cle.com>, linux-rdma@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH for-next] RDMA/cm: Rate limit destroy CM ID timeout error message

Does this happen when there is a missing send completion?

Asking because I remember triggering this if a device encounters an
unrecoverable
error/VF reset while under heavy RDMA-CM activity (like a large scale
MPI wire-up).

I assumed it was because RDMA-CM was waiting for TX completions that
would never arrive.

Of course, the unrecoverable error/VF reset without generating flush
completions was the real
bug in my case.

- Jake