From: Jason Gunthorpe <jgg@ziepe.ca>
To: Haakon Bugge <haakon.bugge@oracle.com>
Cc: Sean Hefty <shefty@nvidia.com>, Jacob Moroni <jmoroni@google.com>,
Leon Romanovsky <leon@kernel.org>,
Vlad Dumitrescu <vdumitrescu@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>,
Manjunath Patil <manjunath.b.patil@oracle.com>,
OFED mailing list <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH for-next] RDMA/cm: Rate limit destroy CM ID timeout error message
Date: Thu, 16 Oct 2025 15:01:08 -0300 [thread overview]
Message-ID: <20251016180108.GO3938986@ziepe.ca> (raw)
In-Reply-To: <6244F8C9-2067-4A8A-8DCD-02A4A2D117F6@oracle.com>
On Thu, Oct 16, 2025 at 04:43:16PM +0000, Haakon Bugge wrote:
> Well, I started off this thread thinking a cm_deref_id() was missing
> somewhere, but now I am more inclined to think as you do, this is an
> unrecoverable situation, and I should work with NVIDIA to fix it.
If the VF is just stuck and not progressing QPs for whatever reason
then yes absolutely.
At best all we can do is detect stuck QPs and try to recover them as I
described.
How hard/costly would it be to have a tx timer watchdog on the mad
layer send q?
At the very least we could log a stuck MAD QP..
Jason
next prev parent reply other threads:[~2025-10-16 18:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 10:05 [PATCH for-next] RDMA/cm: Rate limit destroy CM ID timeout error message Håkon Bugge
2025-09-12 19:27 ` yanjun.zhu
2025-09-15 7:43 ` Leon Romanovsky
2025-09-15 9:44 ` Haakon Bugge
2025-09-16 14:18 ` Jason Gunthorpe
2025-09-16 14:36 ` Jacob Moroni
2025-09-25 11:29 ` Haakon Bugge
2025-10-13 14:04 ` Haakon Bugge
2025-10-15 11:38 ` Haakon Bugge
2025-10-15 16:49 ` Jason Gunthorpe
2025-10-15 18:34 ` Sean Hefty
2025-10-15 18:45 ` Jason Gunthorpe
2025-10-16 15:25 ` Haakon Bugge
2025-10-16 16:12 ` Jason Gunthorpe
2025-10-16 16:43 ` Haakon Bugge
2025-10-16 18:01 ` Jason Gunthorpe [this message]
2025-10-21 16:32 ` Haakon Bugge
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=20251016180108.GO3938986@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=haakon.bugge@oracle.com \
--cc=jmoroni@google.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=manjunath.b.patil@oracle.com \
--cc=ohartoov@nvidia.com \
--cc=shefty@nvidia.com \
--cc=vdumitrescu@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