From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v2 0/7] for bpf-next
Date: Thu, 19 May 2022 16:25:11 +0800 [thread overview]
Message-ID: <cover.1652948238.git.geliang.tang@suse.com> (raw)
v2:
- The series is for bpf-next v5.
- patch 1, keep bpf_mptcp_sock_from_subflow() in bpf.c
- patch 3, Drop the 'msg' parameter of verify_sk
- base-commit: df896c77f02a ("DO-NOT-MERGE: git markup: features
net-next-next"), export/20220517T155019
- The last squash-to patch is for "BPF packet scheduler" series.
v1:
- The first 10 patches is for bpf-next v5.
- Rebased the "BPF packet scheduler" series on export branch.
Geliang Tang (6):
bpf: add bpf_skc_to_mptcp_sock_proto
selftests/bpf: Enable CONFIG_IKCONFIG_PROC in config
selftests/bpf: test bpf_skc_to_mptcp_sock
selftests/bpf: verify token of struct mptcp_sock
selftests/bpf: verify ca_name of struct mptcp_sock
selftests/bpf: verify first of struct mptcp_sock
Nicolas Rybowski (1):
selftests/bpf: add MPTCP test base
MAINTAINERS | 1 +
include/linux/bpf.h | 1 +
include/linux/btf_ids.h | 3 +-
include/net/mptcp.h | 6 +
include/uapi/linux/bpf.h | 7 +
kernel/bpf/verifier.c | 1 +
kernel/trace/bpf_trace.c | 2 +
net/core/filter.c | 18 ++
net/mptcp/Makefile | 2 +
net/mptcp/bpf.c | 21 +++
scripts/bpf_doc.py | 2 +
tools/include/uapi/linux/bpf.h | 7 +
tools/testing/selftests/bpf/bpf_tcp_helpers.h | 13 ++
tools/testing/selftests/bpf/config | 3 +
tools/testing/selftests/bpf/network_helpers.c | 40 +++-
tools/testing/selftests/bpf/network_helpers.h | 2 +
.../testing/selftests/bpf/prog_tests/mptcp.c | 174 ++++++++++++++++++
.../testing/selftests/bpf/progs/mptcp_sock.c | 89 +++++++++
18 files changed, 382 insertions(+), 10 deletions(-)
create mode 100644 net/mptcp/bpf.c
create mode 100644 tools/testing/selftests/bpf/prog_tests/mptcp.c
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_sock.c
--
2.34.1
next reply other threads:[~2022-05-19 8:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 8:25 Geliang Tang [this message]
2022-05-19 8:25 ` [PATCH mptcp-next v2 1/7] bpf: add bpf_skc_to_mptcp_sock_proto Geliang Tang
2022-05-19 8:25 ` [PATCH mptcp-next v2 2/7] selftests/bpf: Enable CONFIG_IKCONFIG_PROC in config Geliang Tang
2022-05-19 8:25 ` [PATCH mptcp-next v2 3/7] selftests/bpf: add MPTCP test base Geliang Tang
2022-05-19 8:25 ` [PATCH mptcp-next v2 4/7] selftests/bpf: test bpf_skc_to_mptcp_sock Geliang Tang
2022-05-19 8:25 ` [PATCH mptcp-next v2 5/7] selftests/bpf: verify token of struct mptcp_sock Geliang Tang
2022-05-19 8:25 ` [PATCH mptcp-next v2 6/7] selftests/bpf: verify ca_name " Geliang Tang
2022-05-19 8:25 ` [PATCH mptcp-next v2 7/7] selftests/bpf: verify first " Geliang Tang
2022-05-19 8:25 ` [PATCH mptcp-next v2] Squash to "selftests/bpf: add bpf_first test" Geliang Tang
2022-05-19 10:49 ` Squash to "selftests/bpf: add bpf_first test": Tests Results MPTCP CI
2022-05-19 14:12 ` [PATCH mptcp-next v2 0/7] for bpf-next Matthieu Baerts
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.1652948238.git.geliang.tang@suse.com \
--to=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.