[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230227101504.45ef890c@kernel.org>
Date: Mon, 27 Feb 2023 10:15:04 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Brian Haley <haleyb.dev@...il.com>, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, corbet@....net,
den@...nvz.org, razor@...ckwall.org, ulf.hansson@...aro.org,
Jason@...c4.com, wangyuweihx@...il.com, daniel@...earbox.net,
thomas.zeitlhofer+lkml@...it.at, alexander@...alicyn.com,
ja@....bg, netdev@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 6.2 31/53] neighbor: fix proxy_delay usage when
it is zero
On Sun, 26 Feb 2023 09:44:23 -0500 Sasha Levin wrote:
> From: Brian Haley <haleyb.dev@...il.com>
>
> [ Upstream commit 62e395f82d04510b0f86e5e603e29412be88596f ]
>
> When set to zero, the neighbor sysctl proxy_delay value
> does not cause an immediate reply for ARP/ND requests
> as expected, it instead causes a random delay between
> [0, U32_MAX). Looking at this comment from
> __get_random_u32_below() explains the reason:
Potential behavior change, can we wait 4 weeks, until it's been
in a couple of -rcs?
Powered by blists - more mailing lists