From: patchwork-bot+netdevbpf@kernel.org
To: Paul Chaignon <paul@isovalent.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
martin.lau@linux.dev, john.fastabend@gmail.com,
fankaixi.li@bytedance.com, razor@blackwall.org, yhs@fb.com
Subject: Re: [PATCH bpf-next v3 0/5] bpf: Allow any source IP in bpf_skb_set_tunnel_key
Date: Tue, 26 Jul 2022 10:50:30 +0000 [thread overview]
Message-ID: <165883263082.5700.11737632699729605210.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1658759380.git.paul@isovalent.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 25 Jul 2022 16:31:07 +0200 you wrote:
> Commit 26101f5ab6bd ("bpf: Add source ip in "struct bpf_tunnel_key"")
> added support for getting and setting the outer source IP of encapsulated
> packets via the bpf_skb_{get,set}_tunnel_key BPF helper. This change
> allows BPF programs to set any IP address as the source, including for
> example the IP address of a container running on the same host.
>
> In that last case, however, the encapsulated packets are dropped when
> looking up the route because the source IP address isn't assigned to any
> interface on the host. To avoid this, we need to set the
> FLOWI_FLAG_ANYSRC flag.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/5] ip_tunnels: Add new flow flags field to ip_tunnel_key
https://git.kernel.org/bpf/bpf-next/c/451ef36bd229
- [bpf-next,v3,2/5] vxlan: Use ip_tunnel_key flow flags in route lookups
https://git.kernel.org/bpf/bpf-next/c/7e2fb8bc7ef6
- [bpf-next,v3,3/5] geneve: Use ip_tunnel_key flow flags in route lookups
https://git.kernel.org/bpf/bpf-next/c/861396ac0b47
- [bpf-next,v3,4/5] bpf: Set flow flag to allow any source IP in bpf_tunnel_key
https://git.kernel.org/bpf/bpf-next/c/b8fff748521c
- [bpf-next,v3,5/5] selftests/bpf: Don't assign outer source IP to host
https://git.kernel.org/bpf/bpf-next/c/1115169f47ae
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-26 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 14:31 [PATCH bpf-next v3 0/5] bpf: Allow any source IP in bpf_skb_set_tunnel_key Paul Chaignon
2022-07-25 14:31 ` [PATCH bpf-next v3 1/5] ip_tunnels: Add new flow flags field to ip_tunnel_key Paul Chaignon
2022-07-25 14:31 ` [PATCH bpf-next v3 2/5] vxlan: Use ip_tunnel_key flow flags in route lookups Paul Chaignon
2022-07-25 14:32 ` [PATCH bpf-next v3 3/5] geneve: " Paul Chaignon
2022-07-25 14:32 ` [PATCH bpf-next v3 4/5] bpf: Set flow flag to allow any source IP in bpf_tunnel_key Paul Chaignon
2022-07-25 14:32 ` [PATCH bpf-next v3 5/5] selftests/bpf: Don't assign outer source IP to host Paul Chaignon
2022-07-26 10:50 ` 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=165883263082.5700.11737632699729605210.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=fankaixi.li@bytedance.com \
--cc=john.fastabend@gmail.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=paul@isovalent.com \
--cc=razor@blackwall.org \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox