netdev - Re: [PATCH RESEND] icmp: Add counters for rate limits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 26 Jan 2023 10:30:17 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jamie Bainbridge <jamie.bainbridge@...il.com>
Cc:     davem@...emloft.net, yoshfuji@...ux-ipv6.org, dsahern@...nel.org,
        edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
        rawal.abhishek92@...il.com, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org
Subject: Re: [PATCH RESEND] icmp: Add counters for rate limits

Hello:

This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@...hat.com>:

On Wed, 25 Jan 2023 11:16:52 +1100 you wrote:
> There are multiple ICMP rate limiting mechanisms:
> 
> * Global limits: net.ipv4.icmp_msgs_burst/icmp_msgs_per_sec
> * v4 per-host limits: net.ipv4.icmp_ratelimit/ratemask
> * v6 per-host limits: net.ipv6.icmp_ratelimit/ratemask
> 
> However, when ICMP output is limited, there is no way to tell
> which limit has been hit or even if the limits are responsible
> for the lack of ICMP output.
> 
> [...]

Here is the summary with links:
  - [RESEND] icmp: Add counters for rate limits
    https://git.kernel.org/netdev/net-next/c/d0941130c935

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html