From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v4 0/5] Squash to "Add mptcp_subflow bpf_iter support"
Date: Thu, 06 Mar 2025 09:50:18 +0800 [thread overview]
Message-ID: <e6f4c2e46d6089e4b76fe8a0e8b83557ddfd53de.camel@kernel.org> (raw)
In-Reply-To: <cover.1740368110.git.tanggeliang@kylinos.cn>
Hi Matt,
On Mon, 2025-02-24 at 11:37 +0800, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v4:
> - drop sock_owned_by_user_nocheck and spin_is_locked. According to
> comments from Mat and Martin, in this set mptcp_subflow
> bpf_iter only used from a cg sockopt bpf prog, no need to add
> these
> check at this moment.
>
> v3:
> - patch 3, continue to use sock_owned_by_user_nocheck() and
> spin_is_locked()
> checks instead of using msk_owned_by_me().
> - patch 5, drop declaration of bpf_mptcp_subflow_tcp_sock. It's no
> longer
> used.
> - patch 5, update the comment for mptcp_subflow_tcp_sock(), which is
> a BPF
> helper, not a kfunc.
>
> The commit log of "bpf: Register mptcp common kfunc set" doesn't
> match the
> code, please update it as:
>
> '''
> bpf: Register mptcp common kfunc set
>
> MPTCP helper mptcp_subflow_ctx() is used to convert struct sock to
> struct mptcp_subflow_context. It will be used in MPTCP BPF programs.
>
> This patch defines corresponding wrapper of this helper, and put it
> into the newly defined mptcp common kfunc set and register this set
> with the flag BPF_PROG_TYPE_CGROUP_SOCKOPT to let it accessible to
> the 'cgroup/getsockopt' type of BPF programs.
> '''
Thanks for applying this set. Please update this commit log too.
-Geliang
>
> v2:
> - Drop bpf_skc_to_mptcp_sock
> - Check the owner before assigning the msk as Mat suggested.
> - Use bpf_core_cast() in mptcp_subflow bpf_iter subtest instead of
> using bpf_skc_to_mptcp_sock().
>
> Address Martin's suggestions for "Add mptcp_subflow bpf_iter support"
> v2.
>
> Geliang Tang (5):
> Revert "bpf: Extend bpf_skc_to_mptcp_sock to MPTCP sock"
> Revert "bpf: Allow use of skc_to_mptcp_sock in cg_sockopt"
> Squash to "bpf: Add mptcp_subflow bpf_iter"
> Revert "bpf: Acquire and release mptcp socket"
> 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 ++++-------------
> --
> .../testing/selftests/bpf/bpf_experimental.h | 2 +-
> tools/testing/selftests/bpf/progs/mptcp_bpf.h | 5 ---
> .../selftests/bpf/progs/mptcp_bpf_iters.c | 10 ++---
> 7 files changed, 15 insertions(+), 51 deletions(-)
>
next prev parent reply other threads:[~2025-03-06 1:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 3:37 [PATCH mptcp-next v4 0/5] Squash to "Add mptcp_subflow bpf_iter support" Geliang Tang
2025-02-24 3:37 ` [PATCH mptcp-next v4 1/5] Revert "bpf: Extend bpf_skc_to_mptcp_sock to MPTCP sock" Geliang Tang
2025-02-24 3:37 ` [PATCH mptcp-next v4 2/5] Revert "bpf: Allow use of skc_to_mptcp_sock in cg_sockopt" Geliang Tang
2025-02-24 3:37 ` [PATCH mptcp-next v4 3/5] Squash to "bpf: Add mptcp_subflow bpf_iter" Geliang Tang
2025-02-24 3:37 ` [PATCH mptcp-next v4 4/5] Revert "bpf: Acquire and release mptcp socket" Geliang Tang
2025-02-24 3:37 ` [PATCH mptcp-next v4 5/5] Squash to "selftests/bpf: Add mptcp_subflow bpf_iter subtest" Geliang Tang
2025-02-24 3:56 ` [PATCH mptcp-next v4 0/5] Squash to "Add mptcp_subflow bpf_iter support" Geliang Tang
2025-02-24 4:47 ` MPTCP CI
2025-02-24 11:59 ` Matthieu Baerts
2025-02-26 1:05 ` Mat Martineau
2025-03-05 15:31 ` Matthieu Baerts
2025-03-06 1:50 ` Geliang Tang [this message]
2025-03-06 8:38 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2024-12-09 8:47 Geliang Tang
2024-12-09 9:52 ` MPTCP CI
2024-12-10 11:42 ` 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=e6f4c2e46d6089e4b76fe8a0e8b83557ddfd53de.camel@kernel.org \
--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