From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org, shuah@kernel.org, edumazet@kernel.org,
rdunlap@infradead.org, paulmck@kernel.org, gustavold@gmail.com,
asantostc@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next v4 0/5] netconsole: Support messages ratelimit-ing
Date: Mon, 09 Nov 2026 23:30:25 +0000 [thread overview]
Message-ID: <179426702566.3543549.15081609670268314046.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103-netcons_ratelimit-v4-0-b554c27ba27a@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 03 Nov 2026 02:37:45 -0800 you wrote:
> netconsole hands every console message to every enabled target, with no
> bound on the rate.
>
> At Meta, a few hosts caused some DoS and netconsd was OOM killed in
> some regions, fed by 3 billion RCU messages from thousand hosts and by
> a swap fault that retries forever, which logged 6 million copies of one
> line on a single host in a few hours.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/5] netconsole: send the oops when oops_only is set
https://git.kernel.org/netdev/net-next/c/96178f0437dd
- [net-next,v4,2/5] netconsole: add a per-target message rate limit
https://git.kernel.org/netdev/net-next/c/cfc3ceefdc96
- [net-next,v4,3/5] netconsole: allow configuring the rate limit interval through configfs
https://git.kernel.org/netdev/net-next/c/04d1be8ae2dd
- [net-next,v4,4/5] netconsole: allow configuring the rate limit burst through configfs
https://git.kernel.org/netdev/net-next/c/8481c27649b9
- [net-next,v4,5/5] docs: netconsole: document rate limit feature
https://git.kernel.org/netdev/net-next/c/ec1e576cd88d
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:[~2026-11-09 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 10:37 Breno Leitao
2026-11-03 10:37 ` [PATCH net-next v4 1/5] netconsole: send the oops when oops_only is set Breno Leitao
2026-11-03 10:37 ` [PATCH net-next v4 2/5] netconsole: add a per-target message rate limit Breno Leitao
2026-11-03 10:37 ` [PATCH net-next v4 3/5] netconsole: allow configuring the rate limit interval through configfs Breno Leitao
2026-11-03 10:37 ` [PATCH net-next v4 4/5] netconsole: allow configuring the rate limit burst " Breno Leitao
2026-11-03 10:37 ` [PATCH net-next v4 5/5] docs: netconsole: document rate limit feature Breno Leitao
2026-11-09 23:30 ` 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=179426702566.3543549.15081609670268314046.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gustavold@gmail.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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®