From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v6 0/4] add skc_to_mptcp_sock
Date: Sun, 6 Mar 2022 09:01:33 +0800 [thread overview]
Message-ID: <cover.1646528337.git.geliang.tang@suse.com> (raw)
v6:
- add skc_to_mptcp_sock helper and test
RESEND:
- fix the CI Build Failure.
v5:
- fix incorrect token value
- verify the token in selftest
v4:
- define bpf_mptcp_sock_proto as a static function, no longer export
it in linux/bpf.h
v3:
- use RET_PTR_TO_BTF_ID_OR_NULL instead of RET_PTR_TO_MPTCP_SOCK_OR_NULL
- add a new bpf_id BTF_SOCK_TYPE_MPTCP
v2:
- keep RET_PTR_TO_MPTCP_SOCK_OR_NULL. If we use RET_PTR_TO_BTF_ID_OR_NULL
instead of RET_PTR_TO_MPTCP_SOCK_OR_NULL as Alexei suggested, the
"userspace" tests developed by Nicolas will break.
Geliang Tang (4):
Revert "selftests: bpf: add bpf_mptcp_sock() verifier tests"
Revert "bpf: add 'bpf_mptcp_sock' structure and helper"
bpf: add skc_to_mptcp_sock helper
selftests: bpf: add skc_to_mptcp_sock test
include/linux/bpf.h | 31 +--------
include/linux/btf_ids.h | 3 +-
include/uapi/linux/bpf.h | 14 ++--
kernel/bpf/verifier.c | 20 ------
net/core/filter.c | 21 ++++--
net/mptcp/bpf.c | 67 ++-----------------
scripts/bpf_doc.py | 4 +-
tools/include/uapi/linux/bpf.h | 14 ++--
tools/testing/selftests/bpf/bpf_tcp_helpers.h | 6 ++
.../testing/selftests/bpf/prog_tests/mptcp.c | 27 ++++++--
tools/testing/selftests/bpf/progs/mptcp.c | 23 +++++++
tools/testing/selftests/bpf/verifier/sock.c | 63 -----------------
12 files changed, 89 insertions(+), 204 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-06 1:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 1:01 Geliang Tang [this message]
2022-03-06 1:01 ` [PATCH mptcp-next v6 1/4] Revert "selftests: bpf: add bpf_mptcp_sock() verifier tests" Geliang Tang
2022-03-06 1:01 ` [PATCH mptcp-next v6 2/4] Revert "bpf: add 'bpf_mptcp_sock' structure and helper" Geliang Tang
2022-03-06 1:01 ` [PATCH mptcp-next v6 3/4] bpf: add skc_to_mptcp_sock helper Geliang Tang
2022-03-07 14:04 ` Matthieu Baerts
2022-03-07 14:29 ` Geliang Tang
2022-03-06 1:01 ` [PATCH mptcp-next v6 4/4] selftests: bpf: add skc_to_mptcp_sock test Geliang Tang
2022-03-06 1:48 ` selftests: bpf: add skc_to_mptcp_sock test: Tests Results MPTCP CI
2022-03-06 1:48 ` MPTCP CI
2022-03-07 12:27 ` MPTCP CI
2022-03-07 14:15 ` [PATCH mptcp-next v6 4/4] selftests: bpf: add skc_to_mptcp_sock test Matthieu Baerts
2022-03-07 15:58 ` Geliang Tang
2022-03-07 16:15 ` 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.1646528337.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.