Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp2931926ybk; Mon, 18 May 2020 11:24:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwFvmULtjdBG6+/J3EXnkfGAz1k23BfHGIcrGG/JgaFrRuO57pSm4hHzxBBqduT1siMe8R0 X-Received: by 2002:a50:fd97:: with SMTP id o23mr14846766edt.363.1589826276350; Mon, 18 May 2020 11:24:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589826276; cv=none; d=google.com; s=arc-20160816; b=quUQHBB3lYHUU1CDILk+ILuDiHFDfvSYEIdx1UKe3uzVAtiCG/ffYaPPxEXyiiszvh 7N+xBBthro5YklaWhxzajRaTdb/bz1BBAoFF/cpvlQO+Xt384yLpvQh8bEhWjloHlVuV GkcPKRReJj+QfmET+YZ7LRakA0xNoIJMhRXcAgRg3SpWRAnDgj/6CgjjYaXydUqHlN2F l0NiBpOhZMhP9fJYTqgrzendDNQ1XAcscMtZ+45HGoJWDvMDIoudDQx9osp8pP/MquO0 vzoAyldT7X4fyluX+9cCbxLTSr3ekFnwrogpe6Cncx3mVgViOjX1LDgVzIq2Js33b+6+ y1HQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=kc88UD8YjsbCACTyxP4gkAPj7+h+5lfe9ZCkTR8dn7E=; b=dshdGeMkW9lo7S1FqGCgPfeIJnjKH7K9tJfL6FsmXE91r6ObeInFLFgmE0Uo7/sRaH GPRMQ3KzvP0pKfmppYkMsGnJAbuRRPpfblP4FROkJJEvsXTpLsdOpqhzHCVwjO8vI68e /qsvw5e+MZOIDbMJWKJAJ/OhgLktFyZna0w33Ez8RrPjEYJjilH/M2CnGMFONNc2dTqA 7xZ3tLy5NNGzZypRdnzPT0c9PSAxP4jNV0EEDMEO/90Ri1znI8NNpquj/Z/1uHfOue8V DMwNnkDQrN7/9mtWDq8j3JwP3cs4f6ivbYNyoovta0RaaOIcLGLpdEV/A05ELCRLbu7m +Ysw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="dd7S/zye"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j23si3110356ejs.4.2020.05.18.11.24.13; Mon, 18 May 2020 11:24:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="dd7S/zye"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731805AbgERSWI (ORCPT + 99 others); Mon, 18 May 2020 14:22:08 -0400 Received: from mail.kernel.org ([198.145.29.99]:53252 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730721AbgERRux (ORCPT ); Mon, 18 May 2020 13:50:53 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 26FE120826; Mon, 18 May 2020 17:50:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1589824252; bh=fE4l/YiFzGqBGD1qlBVhUzgpbiM6XFdUJWqpCgy6Krk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=dd7S/zyem6cQlEgG3GICtblWa3wrLNL3l7rMJ2VZRt0YP8GPS5sIzFHapJcTkd92X 8Uo4KL/k2j8u1FcbMYE4LfG39bQ3W8+JSZGQWaFYwzdDCSipsAu99nQQ35qRYAxriE MaFVPL2/Una8lhul1G2LZmrY6IdgdPWfnMlyqG14= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Paolo Abeni , Jakub Kicinski , Colin Walters Subject: [PATCH 4.19 18/80] net: ipv4: really enforce backoff for redirects Date: Mon, 18 May 2020 19:36:36 +0200 Message-Id: <20200518173454.103849772@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200518173450.097837707@linuxfoundation.org> References: <20200518173450.097837707@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Paolo Abeni [ Upstream commit 57644431a6c2faac5d754ebd35780cf43a531b1a ] 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: Greg Kroah-Hartman --- net/ipv4/route.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/net/ipv4/route.c +++ b/net/ipv4/route.c @@ -906,7 +906,7 @@ void ip_rt_send_redirect(struct sk_buff /* Check for load limit; set rate_last to the latest sent * redirect. */ - if (peer->rate_tokens == 0 || + if (peer->n_redirects == 0 || time_after(jiffies, (peer->rate_last + (ip_rt_redirect_load << peer->n_redirects)))) {