From: patchwork-bot+netdevbpf@kernel.org
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, dsahern@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net v4 0/4] vrf: fix source address selection with route leak
Date: Sun, 14 Jul 2024 14:41:35 +0000 [thread overview]
Message-ID: <172096809576.533.5025481642505106509.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240710081521.3809742-1-nicolas.dichtel@6wind.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 10 Jul 2024 10:14:26 +0200 you wrote:
> For patch 1 and 2, I didn't find the exact commit that introduced this bug, but
> I suspect it has been here since the first version. I arbitrarily choose one.
>
> v3 -> v4:
> patch 2: set 'dev' only when needed
>
> v2 -> v3:
> patch 1: enforce 80 columns limit
> patch 2: fix coding style
> patch 4: add tcp and udp tests
>
> [...]
Here is the summary with links:
- [net,v4,1/4] ipv4: fix source address selection with route leak
https://git.kernel.org/netdev/net/c/680735235356
- [net,v4,2/4] ipv6: fix source address selection with route leak
https://git.kernel.org/netdev/net/c/252442f2ae31
- [net,v4,3/4] ipv6: take care of scope when choosing the src addr
https://git.kernel.org/netdev/net/c/abb9a68d2c64
- [net,v4,4/4] selftests: vrf_route_leaking: add local test
https://git.kernel.org/netdev/net/c/39367183aecf
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:[~2024-07-14 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 8:14 [PATCH net v4 0/4] vrf: fix source address selection with route leak Nicolas Dichtel
2024-07-10 8:14 ` [PATCH net v4 1/4] ipv4: " Nicolas Dichtel
2024-07-10 8:14 ` [PATCH net v4 2/4] ipv6: " Nicolas Dichtel
2024-07-10 8:14 ` [PATCH net v4 3/4] ipv6: take care of scope when choosing the src addr Nicolas Dichtel
2024-07-10 8:14 ` [PATCH net v4 4/4] selftests: vrf_route_leaking: add local test Nicolas Dichtel
2024-07-14 14:41 ` 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=172096809576.533.5025481642505106509.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--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.