From: Daniel Borkmann <daniel@iogearbox.net>
To: ast@kernel.org
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, rdna@fb.com,
sdf@google.com, andrii.nakryiko@gmail.com,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf-next v2 0/4] Add get{peer,sock}name cgroup attach types
Date: Tue, 19 May 2020 00:45:44 +0200 [thread overview]
Message-ID: <cover.1589841594.git.daniel@iogearbox.net> (raw)
Trivial patch to add get{peer,sock}name cgroup attach types to the BPF
sock_addr programs in order to enable rewriting sockaddr structs from
both calls along with libbpf and bpftool support as well as selftests.
Thanks!
v1 -> v2:
- use __u16 for ports in start_server_with_port() signature and in
expected_{local,peer} ports in the test case (Andrey)
- Added both Andrii's and Andrey's ACKs
Daniel Borkmann (4):
bpf: add get{peer,sock}name attach types for sock_addr
bpf, libbpf: enable get{peer,sock}name attach types
bpf, bpftool: enable get{peer,sock}name attach types
bpf, testing: add get{peer,sock}name selftests to test_progs
include/linux/bpf-cgroup.h | 1 +
include/uapi/linux/bpf.h | 4 +
kernel/bpf/syscall.c | 12 ++
kernel/bpf/verifier.c | 6 +-
net/core/filter.c | 4 +
net/ipv4/af_inet.c | 8 +-
net/ipv6/af_inet6.c | 9 +-
.../bpftool/Documentation/bpftool-cgroup.rst | 10 +-
.../bpftool/Documentation/bpftool-prog.rst | 3 +-
tools/bpf/bpftool/bash-completion/bpftool | 15 ++-
tools/bpf/bpftool/cgroup.c | 7 +-
tools/bpf/bpftool/main.h | 4 +
tools/bpf/bpftool/prog.c | 6 +-
tools/include/uapi/linux/bpf.h | 4 +
tools/lib/bpf/libbpf.c | 8 ++
tools/testing/selftests/bpf/network_helpers.c | 11 +-
tools/testing/selftests/bpf/network_helpers.h | 1 +
.../bpf/prog_tests/connect_force_port.c | 107 +++++++++++++-----
.../selftests/bpf/progs/connect_force_port4.c | 59 +++++++++-
.../selftests/bpf/progs/connect_force_port6.c | 70 +++++++++++-
20 files changed, 295 insertions(+), 54 deletions(-)
--
2.21.0
next reply other threads:[~2020-05-18 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 22:45 Daniel Borkmann [this message]
2020-05-18 22:45 ` [PATCH bpf-next v2 1/4] bpf: add get{peer,sock}name attach types for sock_addr Daniel Borkmann
2020-05-18 22:45 ` [PATCH bpf-next v2 2/4] bpf, libbpf: enable get{peer,sock}name attach types Daniel Borkmann
2020-05-18 22:45 ` [PATCH bpf-next v2 3/4] bpf, bpftool: " Daniel Borkmann
2020-05-18 22:45 ` [PATCH bpf-next v2 4/4] bpf, testing: add get{peer,sock}name selftests to test_progs Daniel Borkmann
2020-05-19 18:39 ` [PATCH bpf-next v2 0/4] Add get{peer,sock}name cgroup attach types Alexei Starovoitov
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=cover.1589841594.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdna@fb.com \
--cc=sdf@google.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;
as well as URLs for NNTP newsgroup(s).