From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v5 0/5] Squash to "Add mptcp_subflow bpf_iter support"
Date: Wed, 11 Dec 2024 11:11:51 +0800 [thread overview]
Message-ID: <cover.1733886326.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v5:
- update subjects and commit logs as Matt suggested (thanks).
- avoid repeating checks in patch 1.
- do stricter checks on subflows in patch 3.
v4:
- CI reports the following BUILD_BUG_ON fails on i386:
BUILD_BUG_ON(sizeof(struct bpf_iter_mptcp_subflow_kern) !=
sizeof(struct bpf_iter_mptcp_subflow))
Just like in bpf_iter_task_new(), change this "!=" to ">".
v3:
- check sock_owned_by_user_nocheck(sk)/spin_is_locked(&sk->sk_lock.slock),
instead of lockdep_sock_is_held(sk).
- add "sizeof" and "alignof" checks.
- drop bpf_mptcp_sk() and bpf_mptcp_subflow_tcp_sock() definitions. Use
bpf_skc_to_mptcp_sock() and mptcp_subflow_tcp_sock() in mptcp_subflow
bpf_iter selftests instead.
v2:
- add CONFIG_LOCKDEP check in patch 2 to fix the build error reported
by CI.
Address Martin's comments in v1.
Geliang Tang (5):
bpf: Extend bpf_skc_to_mptcp_sock to MPTCP sock
bpf: Allow use of skc_to_mptcp_sock in cg_sockopt
Squash to "bpf: Register mptcp common kfunc set"
Squash to "bpf: Add mptcp_subflow bpf_iter"
Squash to "selftests/bpf: Add mptcp_subflow bpf_iter subtest"
include/net/mptcp.h | 4 +-
kernel/bpf/cgroup.c | 2 +
net/core/filter.c | 2 +-
net/mptcp/bpf.c | 41 +++++++++++--------
tools/testing/selftests/bpf/progs/mptcp_bpf.h | 1 -
.../selftests/bpf/progs/mptcp_bpf_iters.c | 11 +++--
6 files changed, 33 insertions(+), 28 deletions(-)
--
2.45.2
next reply other threads:[~2024-12-11 3:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 3:11 Geliang Tang [this message]
2024-12-11 3:11 ` [PATCH mptcp-next v5 1/5] bpf: Extend bpf_skc_to_mptcp_sock to MPTCP sock Geliang Tang
2024-12-11 3:11 ` [PATCH mptcp-next v5 2/5] bpf: Allow use of skc_to_mptcp_sock in cg_sockopt Geliang Tang
2024-12-11 3:11 ` [PATCH mptcp-next v5 3/5] Squash to "bpf: Register mptcp common kfunc set" Geliang Tang
2024-12-11 3:11 ` [PATCH mptcp-next v5 4/5] Squash to "bpf: Add mptcp_subflow bpf_iter" Geliang Tang
2024-12-11 3:11 ` [PATCH mptcp-next v5 5/5] Squash to "selftests/bpf: Add mptcp_subflow bpf_iter subtest" Geliang Tang
2024-12-11 4:17 ` [PATCH mptcp-next v5 0/5] Squash to "Add mptcp_subflow bpf_iter support" MPTCP CI
2024-12-16 12:06 ` Matthieu Baerts
2024-12-16 12:27 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2025-03-03 10:33 Geliang Tang
2025-03-03 11:13 ` Matthieu Baerts
2025-03-03 11:42 ` MPTCP CI
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.1733886326.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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