From: Leon Romanovsky <leon@kernel.org>
To: "Jason Gunthorpe" <jgg@ziepe.ca>,
"Sean Hefty" <shefty@nvidia.com>,
"Vlad Dumitrescu" <vdumitrescu@nvidia.com>,
"Or Har-Toov" <ohartoov@nvidia.com>,
"Jacob Moroni" <jmoroni@google.com>,
"Manjunath Patil" <manjunath.b.patil@oracle.com>,
"Håkon Bugge" <haakon.bugge@oracle.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next] RDMA/cm: Rate limit destroy CM ID timeout error message
Date: Mon, 15 Sep 2025 03:43:02 -0400 [thread overview]
Message-ID: <175792218281.1172128.11777926053050212672.b4-ty@kernel.org> (raw)
In-Reply-To: <20250912100525.531102-1-haakon.bugge@oracle.com>
On Fri, 12 Sep 2025 12:05:20 +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().
>
>
Applied, thanks!
[1/1] RDMA/cm: Rate limit destroy CM ID timeout error message
https://git.kernel.org/rdma/rdma/c/2bbe1255fcf19c
Best regards,
--
Leon Romanovsky <leon@kernel.org>
next prev parent reply other threads:[~2025-09-15 7:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 10:05 Håkon Bugge
2025-09-12 19:27 ` yanjun.zhu
2025-09-15 7:43 ` Leon Romanovsky [this message]
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
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=175792218281.1172128.11777926053050212672.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=haakon.bugge@oracle.com \
--cc=jgg@ziepe.ca \
--cc=jmoroni@google.com \
--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
all inboxes | Powered by JetHome®