netdev - Re: [PATCH bpf-next v3 0/5] bpf: Allow any source IP in bpf_skb_set_tunnel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <165883263082.5700.11737632699729605210.git-patchwork-notify@kernel.org>
Date:   Tue, 26 Jul 2022 10:50:30 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Paul Chaignon <paul@...valent.com>
Cc:     ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
        netdev@...r.kernel.org, bpf@...r.kernel.org, martin.lau@...ux.dev,
        john.fastabend@...il.com, fankaixi.li@...edance.com,
        razor@...ckwall.org, yhs@...com
Subject: Re: [PATCH bpf-next v3 0/5] bpf: Allow any source IP in
 bpf_skb_set_tunnel_key

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.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