From: patchwork-bot+netdevbpf@kernel.org
To: Riccardo Paolo Bestetti <pbl@bestov.io>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, cmllamas@google.com,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net] ipv4: fix bind address validity regression tests
Date: Mon, 20 Jun 2022 09:00:13 +0000 [thread overview]
Message-ID: <165571561302.18430.6859728258984876078.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220619162734.113340-1-pbl@bestov.io>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 19 Jun 2022 18:27:35 +0200 you wrote:
> Commit 8ff978b8b222 ("ipv4/raw: support binding to nonlocal addresses")
> introduces support for binding to nonlocal addresses, as well as some
> basic test coverage for some of the related cases.
>
> Commit b4a028c4d031 ("ipv4: ping: fix bind address validity check")
> fixes a regression which incorrectly removed some checks for bind
> address validation. In addition, it introduces regression tests for
> those specific checks. However, those regression tests are defective, in
> that they perform the tests using an incorrect combination of bind
> flags. As a result, those tests fail when they should succeed.
>
> [...]
Here is the summary with links:
- [v2,net] ipv4: fix bind address validity regression tests
https://git.kernel.org/netdev/net/c/313c502fa3b3
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:[~2022-06-20 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 16:27 [PATCH v2 net] ipv4: fix bind address validity regression tests Riccardo Paolo Bestetti
2022-06-20 9:00 ` 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=165571561302.18430.6859728258984876078.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cmllamas@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pbl@bestov.io \
--cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox