From: Stanislav Fomichev <sdf@google.com>
To: netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net,
Stanislav Fomichev <sdf@google.com>, Andrey Ignatov <rdna@fb.com>
Subject: [PATCH bpf-next 0/4] bpf: allow any port in bpf_bind helper
Date: Mon, 4 May 2020 10:34:26 -0700 [thread overview]
Message-ID: <20200504173430.6629-1-sdf@google.com> (raw)
We want to have a tighter control on what ports we bind to in
the BPF_CGROUP_INET{4,6}_CONNECT hooks even if it means
connect() becomes slightly more expensive.
The series goes like this:
1. selftests: move existing helpers that make it easy to create
listener threads into common test_progs part
2. selftests: make sure the helpers above don't get stuck forever
in case the tests fails
3. do small refactoring of __inet{,6}_bind() flags to make it easy
to extend them with the additional flags
4. remove the restriction on port being zero in bpf_bind() helper;
add new bind flag to prevent POST_BIND hook from being called
Cc: Andrey Ignatov <rdna@fb.com>
Stanislav Fomichev (4):
selftests/bpf: generalize helpers to control backround listener
selftests/bpf: adopt accept_timeout from sockmap_listen
net: refactor arguments of inet{,6}_bind
bpf: allow any port in bpf_bind helper
include/net/inet_common.h | 8 +-
include/net/ipv6_stubs.h | 2 +-
net/core/filter.c | 15 +-
net/ipv4/af_inet.c | 20 ++-
net/ipv6/af_inet6.c | 22 +--
.../bpf/prog_tests/connect_force_port.c | 104 +++++++++++
.../selftests/bpf/prog_tests/sockmap_listen.c | 34 ----
.../selftests/bpf/prog_tests/tcp_rtt.c | 115 +-----------
.../selftests/bpf/progs/connect_force_port4.c | 28 +++
.../selftests/bpf/progs/connect_force_port6.c | 28 +++
tools/testing/selftests/bpf/test_progs.c | 165 ++++++++++++++++++
tools/testing/selftests/bpf/test_progs.h | 7 +
12 files changed, 372 insertions(+), 176 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/connect_force_port.c
create mode 100644 tools/testing/selftests/bpf/progs/connect_force_port4.c
create mode 100644 tools/testing/selftests/bpf/progs/connect_force_port6.c
--
2.26.2.526.g744177e7f7-goog
next reply other threads:[~2020-05-04 17:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 17:34 Stanislav Fomichev [this message]
2020-05-04 17:34 ` [PATCH bpf-next 1/4] selftests/bpf: generalize helpers to control backround listener Stanislav Fomichev
2020-05-05 6:23 ` Andrii Nakryiko
2020-05-05 16:08 ` sdf
2020-05-05 18:50 ` Andrii Nakryiko
2020-05-04 17:34 ` [PATCH bpf-next 2/4] selftests/bpf: adopt accept_timeout from sockmap_listen Stanislav Fomichev
2020-05-04 17:34 ` [PATCH bpf-next 3/4] net: refactor arguments of inet{,6}_bind Stanislav Fomichev
2020-05-05 18:16 ` Martin KaFai Lau
2020-05-05 18:19 ` Stanislav Fomichev
2020-05-04 17:34 ` [PATCH bpf-next 4/4] bpf: allow any port in bpf_bind helper Stanislav Fomichev
2020-05-04 23:22 ` Andrey Ignatov
2020-05-05 16:02 ` sdf
2020-05-05 17:09 ` sdf
2020-05-05 17:33 ` Andrey Ignatov
2020-05-05 17:43 ` sdf
2020-05-05 18:20 ` Andrey Ignatov
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=20200504173430.6629-1-sdf@google.com \
--to=sdf@google.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rdna@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;
as well as URLs for NNTP newsgroup(s).