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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250916141812.GP882933@ziepe.ca>
Date: Tue, 16 Sep 2025 11:18:12 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Håkon Bugge <haakon.bugge@...cle.com>
Cc: Leon Romanovsky <leon@...nel.org>, Sean Hefty <shefty@...dia.com>,
	Vlad Dumitrescu <vdumitrescu@...dia.com>,
	Or Har-Toov <ohartoov@...dia.com>,
	Jacob Moroni <jmoroni@...gle.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

On Fri, Sep 12, 2025 at 12:05:20PM +0200, Håkon Bugge wrote:
> When the destroy CM ID timeout kicks in, you typically get a storm of
> them which creates a log flooding. Hence, change pr_err() to
> pr_err_ratelimited() in cm_destroy_id_wait_timeout().

Did you figure out why you were getting these? IIRC it signals a ULP
bug and is not expected.

Jason