From: Corey Minyard <corey@minyard.net>
To: Breno Leitao <leitao@debian.org>
Cc: openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] ipmi: Use dev_warn_ratelimited() for incorrect message warnings
Date: Thu, 10 Jul 2025 08:05:06 -0500 [thread overview]
Message-ID: <aG-6gtCvsowPbH8v@mail.minyard.net> (raw)
In-Reply-To: <20250710-ipmi_ratelimit-v1-1-6d417015ebe9@debian.org>
On Thu, Jul 10, 2025 at 05:57:26AM -0700, Breno Leitao wrote:
> During BMC firmware upgrades on live systems, the ipmi_msghandler
> generates excessive "BMC returned incorrect response" warnings
> while the BMC is temporarily offline. This can flood system logs
> in large deployments.
So the BMC is returning bogus messages during an upgrade? That
sounds like a bug in the BMC, it should either work or be
quiescent. Returning incorrect data can result in bad things
happening.
But, as many thing IPMI, we have to accommodate bad designs.
This change is probably a good idea, anyway.
Queued for next merge window.
Thanks,
-corey
>
> Replace dev_warn() with dev_warn_ratelimited() to throttle these
> warnings and prevent log spam during BMC maintenance operations.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> drivers/char/ipmi/ipmi_msghandler.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c
> index 064944ae9fdc3..8e9050f99e9ef 100644
> --- a/drivers/char/ipmi/ipmi_msghandler.c
> +++ b/drivers/char/ipmi/ipmi_msghandler.c
> @@ -4607,10 +4607,10 @@ static int handle_one_recv_msg(struct ipmi_smi *intf,
> * The NetFN and Command in the response is not even
> * marginally correct.
> */
> - dev_warn(intf->si_dev,
> - "BMC returned incorrect response, expected netfn %x cmd %x, got netfn %x cmd %x\n",
> - (msg->data[0] >> 2) | 1, msg->data[1],
> - msg->rsp[0] >> 2, msg->rsp[1]);
> + dev_warn_ratelimited(intf->si_dev,
> + "BMC returned incorrect response, expected netfn %x cmd %x, got netfn %x cmd %x\n",
> + (msg->data[0] >> 2) | 1, msg->data[1],
> + msg->rsp[0] >> 2, msg->rsp[1]);
>
> goto return_unspecified;
> }
>
> ---
> base-commit: d7b8f8e20813f0179d8ef519541a3527e7661d3a
> change-id: 20250710-ipmi_ratelimit-7e1af5170c57
>
> Best regards,
> --
> Breno Leitao <leitao@debian.org>
>
prev parent reply other threads:[~2025-07-10 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 12:57 Breno Leitao
2025-07-10 13:05 ` Corey Minyard [this message]
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=aG-6gtCvsowPbH8v@mail.minyard.net \
--to=corey@minyard.net \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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®