All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Riccardo Paolo Bestetti <pbl@bestov.io>
Cc: cmllamas@google.com, davem@davemloft.net,
	yoshfuji@linux-ipv6.org, dsahern@kernel.org, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, kernel-team@android.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linmiaohe@huawei.com, maze@google.com
Subject: Re: [PATCH v2] ipv4: ping: fix bind address validity check
Date: Fri, 17 Jun 2022 11:30:13 +0000	[thread overview]
Message-ID: <165546541315.12170.9716012665055247467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220617085435.193319-1-pbl@bestov.io>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 17 Jun 2022 10:54:35 +0200 you wrote:
> Commit 8ff978b8b222 ("ipv4/raw: support binding to nonlocal addresses")
> introduced a helper function to fold duplicated validity checks of bind
> addresses into inet_addr_valid_or_nonlocal(). However, this caused an
> unintended regression in ping_check_bind_addr(), which previously would
> reject binding to multicast and broadcast addresses, but now these are
> both incorrectly allowed as reported in [1].
> 
> [...]

Here is the summary with links:
  - [v2] ipv4: ping: fix bind address validity check
    https://git.kernel.org/netdev/net/c/b4a028c4d031

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2022-06-17 11:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  8:54 [PATCH v2] ipv4: ping: fix bind address validity check Riccardo Paolo Bestetti
2022-06-17 11:30 ` patchwork-bot+netdevbpf [this message]
2022-06-17 23:45   ` Maciej Żenczykowski
2022-06-20 10:11     ` Greg KH
2022-06-23 18:18       ` Maciej Żenczykowski
2022-06-25 14:26         ` Greg KH
2022-06-18  0:32   ` NEEDS FIXING - Was: " Riccardo Paolo Bestetti
2022-06-18  2:58     ` Jakub Kicinski
2022-06-18  7:36       ` Riccardo Paolo Bestetti
2022-06-19 16:44       ` Riccardo Paolo Bestetti
2022-06-17 16:39 ` Carlos Llamas
2022-06-17 18:26   ` Riccardo Paolo Bestetti

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=165546541315.12170.9716012665055247467.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=cmllamas@google.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kernel-team@android.com \
    --cc=kuba@kernel.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maze@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pbl@bestov.io \
    --cc=yoshfuji@linux-ipv6.org \
    /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.