From: patchwork-bot+netdevbpf@kernel•org
To: Mike Manning <mvrmanning@gmail•com>
Cc: netdev@vger•kernel.org, dsahern@kernel•org, jluebbe@lasnet•de
Subject: Re: [PATCH] net: allow unbound socket for packets in VRF when tcp_l3mdev_accept set
Date: Fri, 29 Jul 2022 11:10:13 +0000 [thread overview]
Message-ID: <165909301337.17056.12183027187667104121.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220725181442.18041-1-mvrmanning@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Mon, 25 Jul 2022 19:14:42 +0100 you wrote:
> The commit 3c82a21f4320 ("net: allow binding socket in a VRF when
> there's an unbound socket") changed the inet socket lookup to avoid
> packets in a VRF from matching an unbound socket. This is to ensure the
> necessary isolation between the default and other VRFs for routing and
> forwarding. VRF-unaware processes running in the default VRF cannot
> access another VRF and have to be run with 'ip vrf exec <vrf>'. This is
> to be expected with tcp_l3mdev_accept disabled, but could be reallowed
> when this sysctl option is enabled. So instead of directly checking dif
> and sdif in inet[6]_match, here call inet_sk_bound_dev_eq(). This
> allows a match on unbound socket for non-zero sdif i.e. for packets in
> a VRF, if tcp_l3mdev_accept is enabled.
>
> [...]
Here is the summary with links:
- net: allow unbound socket for packets in VRF when tcp_l3mdev_accept set
https://git.kernel.org/netdev/net/c/944fd1aeacb6
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-07-29 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 18:14 [PATCH] net: allow unbound socket for packets in VRF when tcp_l3mdev_accept set Mike Manning
2022-07-25 18:27 ` David Ahern
2022-07-29 2:56 ` David Ahern
2022-07-29 11: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=165909301337.17056.12183027187667104121.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=dsahern@kernel$(echo .)org \
--cc=jluebbe@lasnet$(echo .)de \
--cc=mvrmanning@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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