From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH RESEND mptcp-next v5 0/3] new bpf_mptcp_sock()
Date: Thu, 3 Mar 2022 23:22:35 +0800 [thread overview]
Message-ID: <cover.1646320786.git.geliang.tang@suse.com> (raw)
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 (3):
Squash to "bpf: add 'bpf_mptcp_sock' structure and helper"
bpf: implement bpf_mptcp_sock()
selftests: bpf: exercise bpf_mptcp_sock()
include/linux/bpf.h | 20 ++-----
include/linux/btf_ids.h | 3 +-
kernel/bpf/verifier.c | 20 -------
net/core/filter.c | 13 +++++
net/mptcp/bpf.c | 52 ++++---------------
.../testing/selftests/bpf/prog_tests/mptcp.c | 27 ++++++++--
tools/testing/selftests/bpf/progs/mptcp.c | 22 ++++++++
7 files changed, 73 insertions(+), 84 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-03 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 15:22 Geliang Tang [this message]
2022-03-03 15:22 ` [PATCH RESEND mptcp-next v5 1/3] Squash to "bpf: add 'bpf_mptcp_sock' structure and helper" Geliang Tang
2022-03-03 15:22 ` [PATCH RESEND mptcp-next v5 2/3] bpf: implement bpf_mptcp_sock() Geliang Tang
2022-03-03 15:52 ` Matthieu Baerts
2022-03-03 15:22 ` [PATCH RESEND mptcp-next v5 3/3] selftests: bpf: exercise bpf_mptcp_sock() Geliang Tang
2022-03-03 15:57 ` selftests: bpf: exercise bpf_mptcp_sock(): Tests Results MPTCP CI
2022-03-07 13:28 ` MPTCP CI
2022-03-03 15:25 ` [PATCH RESEND mptcp-next v5 0/3] new bpf_mptcp_sock() Matthieu Baerts
2022-03-03 15:28 ` Geliang Tang
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.1646320786.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.