From: patchwork-bot+netdevbpf@kernel.org
To: Brian Haley <haleyb.dev@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3] neighbor: fix proxy_delay usage when it is zero
Date: Thu, 02 Feb 2023 05:10:18 +0000 [thread overview]
Message-ID: <167531461893.3090.6533134521882441665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230130171428.367111-1-haleyb.dev@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Jan 2023 12:14:28 -0500 you wrote:
> 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:
>
> /*
> * This function is technically undefined for ceil == 0, and in fact
> * for the non-underscored constant version in the header, we build bug
> * on that. But for the non-constant case, it's convenient to have that
> * evaluate to being a straight call to get_random_u32(), so that
> * get_random_u32_inclusive() can work over its whole range without
> * undefined behavior.
> */
>
> [...]
Here is the summary with links:
- [net-next,v3] neighbor: fix proxy_delay usage when it is zero
https://git.kernel.org/netdev/net-next/c/62e395f82d04
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-02 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 17:14 [PATCH net-next v3] neighbor: fix proxy_delay usage when it is zero Brian Haley
2023-02-02 5:10 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167531461893.3090.6533134521882441665.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haleyb.dev@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.