summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/net/udpgro_fwd.sh
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2021-12-29 12:59:43 -0800
committerJakub Kicinski <kuba@kernel.org>2021-12-29 12:59:44 -0800
commitf7397cd24c5967d24615a28433bbdc9e7e7d57a8 (patch)
treed28b66672917adc72af376b2e1a64b1c1f0e8fa8 /tools/testing/selftests/net/udpgro_fwd.sh
parentfb7bc9204095090731430c8921f9e629740c110a (diff)
parentf83a112bd91a494cdee671aec74e777470fb4a07 (diff)
Merge branch 'net-bridge-mcast-add-and-enforce-query-interval-minimum'
Nikolay Aleksandrov says: ==================== net: bridge: mcast: add and enforce query interval minimum 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. Eric, I looked for the syzbot reports in its dashboard but couldn't find them so I've added you as the reporter. I've prepared a global bridge igmp rate limiting patch but wasn't sure if it's ok for -net. It adds a static limit of 32k packets per second, I plan to send it for net-next with added drop counters for each bridge so it can be easily debugged. Original report can be seen at: https://lore.kernel.org/netdev/e8b9ce41-57b9-b6e2-a46a-ff9c791cf0ba@gmail.com/ ==================== Link: https://lore.kernel.org/r/20211227172116.320768-1-nikolay@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/testing/selftests/net/udpgro_fwd.sh')
0 files changed, 0 insertions, 0 deletions