From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, jiri@resnulli.us
Subject: Re: [PATCH net-next] devlink: make health report on unregistered instance warn just once
Date: Thu, 01 Jun 2023 05:40:21 +0000 [thread overview]
Message-ID: <168559802117.10778.5926262727222751655.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230531015523.48961-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 30 May 2023 18:55:23 -0700 you wrote:
> Devlink health is involved in error recovery. Machines in bad
> state tend to be fairly unreliable, and occasionally get stuck
> in error loops. Even with a reasonable grace period devlink health
> may get a thousand reports in an hour.
>
> In case of reporting on an unregistered devlink instance
> the subsequent reports don't add much value. Switch to
> WARN_ON_ONCE() to avoid flooding dmesg and fleet monitoring
> dashboards.
>
> [...]
Here is the summary with links:
- [net-next] devlink: make health report on unregistered instance warn just once
https://git.kernel.org/netdev/net-next/c/6f4b98147b8d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-06-01 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 1:55 [PATCH net-next] devlink: make health report on unregistered instance warn just once Jakub Kicinski
2023-05-31 6:28 ` Jiri Pirko
2023-06-01 5:40 ` patchwork-bot+netdevbpf [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=168559802117.10778.5926262727222751655.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).