From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com,
stable@vger.kernel.org, herbert@gondor.apana.org.au,
roopa@nvidia.com, davem@davemloft.net,
bridge@lists.linux-foundation.org, kuba@kernel.org
Subject: Re: [PATCH net 0/2] net: bridge: mcast: add and enforce query interval minimum
Date: Wed, 29 Dec 2021 22:20:10 +0000 [thread overview]
Message-ID: <164081641003.5072.12853974016606114194.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211227172116.320768-1-nikolay@nvidia.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 27 Dec 2021 19:21:14 +0200 you wrote:
> Hi,
> This set adds and enforces 1 second minimum value for bridge multicast
> query and startup query intervals in order to avoid rearming the timers
> too often which could lock and crash the host. I doubt anyone is using
> such low values or anything lower than 1 second, so it seems like a good
> minimum. In order to be compatible if the value is lower then it is
> overwritten and a log message is emitted, since we can't return an error
> at this point.
>
> [...]
Here is the summary with links:
- [net,1/2] net: bridge: mcast: add and enforce query interval minimum
https://git.kernel.org/netdev/net/c/99b40610956a
- [net,2/2] net: bridge: mcast: add and enforce startup query interval minimum
https://git.kernel.org/netdev/net/c/f83a112bd91a
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:[~2021-12-29 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 17:21 [PATCH net 0/2] net: bridge: mcast: add and enforce query interval minimum Nikolay Aleksandrov
2021-12-27 17:21 ` [PATCH net 1/2] " Nikolay Aleksandrov
2021-12-28 7:48 ` Greg KH
2022-01-05 18:14 ` Eric Dumazet
2021-12-27 17:21 ` [PATCH net 2/2] net: bridge: mcast: add and enforce startup " Nikolay Aleksandrov
2021-12-28 7:48 ` Greg KH
2021-12-29 22:20 ` 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=164081641003.5072.12853974016606114194.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).