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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 25 Jul 2023 21:20:21 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Lorenz Bauer <lmb@...valent.com>
Cc:     davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
        pabeni@...hat.com, dsahern@...nel.org,
        willemdebruijn.kernel@...il.com, ast@...nel.org,
        daniel@...earbox.net, andrii@...nel.org, martin.lau@...ux.dev,
        song@...nel.org, yhs@...com, john.fastabend@...il.com,
        kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com,
        jolsa@...nel.org, joe@...d.net.nz, mykolal@...com,
        shuah@...nel.org, kuniyu@...zon.com, hemanthmalla@...il.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        bpf@...r.kernel.org, linux-kselftest@...r.kernel.org, joe@...ium.io
Subject: Re: [PATCH bpf-next v6 0/8] Add SO_REUSEPORT support for TC
 bpf_sk_assign

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@...nel.org>:

On Thu, 20 Jul 2023 17:30:04 +0200 you wrote:
> We want to replace iptables TPROXY with a BPF program at TC ingress.
> To make this work in all cases we need to assign a SO_REUSEPORT socket
> to an skb, which is currently prohibited. This series adds support for
> such sockets to bpf_sk_assing.
> 
> I did some refactoring to cut down on the amount of duplicate code. The
> key to this is to use INDIRECT_CALL in the reuseport helpers. To show
> that this approach is not just beneficial to TC sk_assign I removed
> duplicate code for bpf_sk_lookup as well.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,1/8] udp: re-score reuseport groups when connected sockets are present
    https://git.kernel.org/bpf/bpf-next/c/f0ea27e7bfe1
  - [bpf-next,v6,2/8] bpf: reject unhashed sockets in bpf_sk_assign
    https://git.kernel.org/bpf/bpf-next/c/67312adc96b5
  - [bpf-next,v6,3/8] net: export inet_lookup_reuseport and inet6_lookup_reuseport
    https://git.kernel.org/bpf/bpf-next/c/ce796e60b3b1
  - [bpf-next,v6,4/8] net: remove duplicate reuseport_lookup functions
    https://git.kernel.org/bpf/bpf-next/c/0f495f761722
  - [bpf-next,v6,5/8] net: document inet[6]_lookup_reuseport sk_state requirements
    https://git.kernel.org/bpf/bpf-next/c/2a61776366bd
  - [bpf-next,v6,6/8] net: remove duplicate sk_lookup helpers
    https://git.kernel.org/bpf/bpf-next/c/6c886db2e78c
  - [bpf-next,v6,7/8] bpf, net: Support SO_REUSEPORT sockets with bpf_sk_assign
    (no matching commit)
  - [bpf-next,v6,8/8] selftests/bpf: Test that SO_REUSEPORT can be used with sk_assign helper
    https://git.kernel.org/bpf/bpf-next/c/22408d58a42c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ