blob: a0463420cbc7c179af6ad8ecc59d6a160235a10f [file] [log] [blame]
From 4dda52d7af41cddc84d6fdf8a215723fffdfe29d Mon Sep 17 00:00:00 2001
From: Paolo Abeni <>
Date: Fri, 8 May 2020 19:28:34 +0200
Subject: [PATCH] net: ipv4: really enforce backoff for redirects
commit 57644431a6c2faac5d754ebd35780cf43a531b1a upstream.
In commit b406472b5ad7 ("net: ipv4: avoid mixed n_redirects and
rate_tokens usage") I missed the fact that a 0 'rate_tokens' will
bypass the backoff algorithm.
Since rate_tokens is cleared after a redirect silence, and never
incremented on redirects, if the host keeps receiving packets
requiring redirect it will reply ignoring the backoff.
Additionally, the 'rate_last' field will be updated with the
cadence of the ingress packet requiring redirect. If that rate is
high enough, that will prevent the host from generating any
other kind of ICMP messages
The check for a zero 'rate_tokens' value was likely a shortcut
to avoid the more complex backoff algorithm after a redirect
silence period. Address the issue checking for 'n_redirects'
instead, which is incremented on successful redirect, and
does not interfere with other ICMP replies.
Fixes: b406472b5ad7 ("net: ipv4: avoid mixed n_redirects and rate_tokens usage")
Reported-and-tested-by: Colin Walters <>
Signed-off-by: Paolo Abeni <>
Signed-off-by: Jakub Kicinski <>
Signed-off-by: Paul Gortmaker <>
diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index edd352538d69..32f306fe96cb 100644
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
@@ -913,7 +913,7 @@ void ip_rt_send_redirect(struct sk_buff *skb)
/* Check for load limit; set rate_last to the latest sent
* redirect.
- if (peer->rate_tokens == 0 ||
+ if (peer->n_redirects == 0 ||
(peer->rate_last +
(ip_rt_redirect_load << peer->n_redirects)))) {