Files
Eric Dumazet 483397b4ba icmp: change the order of rate limits
commit 8c2bd38b95 upstream.

ICMP messages are ratelimited :

After the blamed commits, the two rate limiters are applied in this order:

1) host wide ratelimit (icmp_global_allow())

2) Per destination ratelimit (inetpeer based)

In order to avoid side-channels attacks, we need to apply
the per destination check first.

This patch makes the following change :

1) icmp_global_allow() checks if the host wide limit is reached.
   But credits are not yet consumed. This is deferred to 3)

2) The per destination limit is checked/updated.
   This might add a new node in inetpeer tree.

3) icmp_global_consume() consumes tokens if prior operations succeeded.

This means that host wide ratelimit is still effective
in keeping inetpeer tree small even under DDOS.

As a bonus, I removed icmp_global.lock as the fast path
can use a lock-free operation.

Fixes: c0303efeab ("net: reduce cycles spend on ICMP replies that gets rate limited")
Fixes: 4cdf507d54 ("icmp: add a global rate limitation")
Reported-by: Keyu Man <keyu.man@email.ucr.edu>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: David Ahern <dsahern@kernel.org>
Cc: Jesper Dangaard Brouer <hawk@kernel.org>
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20240829144641.3880376-2-edumazet@google.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2024-10-04 16:38:50 +02:00
..
2024-06-05 10:18:06 +01:00
2024-05-14 20:21:04 +02:00
2024-07-09 11:31:32 +02:00
2024-06-25 11:10:18 +02:00
2024-05-08 10:35:09 +01:00
2024-05-07 01:35:55 +02:00
2024-10-04 16:38:50 +02:00
2024-07-02 18:59:33 -07:00
2024-04-25 15:24:23 -07:00
2024-04-30 18:32:38 -07:00
2024-05-30 18:29:38 -07:00
2024-05-30 18:29:38 -07:00
2024-06-12 06:39:04 +01:00
2024-07-08 14:07:31 -07:00
2024-05-09 20:25:55 -07:00