From: Geliang Tang <geliang@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v4 4/5] Squash to "bpf: Add mptcp_subflow bpf_iter"
Date: Wed, 11 Dec 2024 11:42:06 +0800 [thread overview]
Message-ID: <271ce327066dd6efe2e3ff793734a23279f26ca4.camel@kernel.org> (raw)
In-Reply-To: <0bf1ea97-64d2-4e0a-b4e7-9627a7d8aa0a@kernel.org>
Hi Matt,
On Tue, 2024-12-10 at 12:48 +0100, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 09/12/2024 09:47, Geliang Tang wrote:
> > From: Geliang Tang <tanggeliang@kylinos.cn>
> >
> > Add "sizeof" and "alignof" checks.
> >
> > Address Martin's comments in v1:
> >
> > - bpf_iter_mptcp_subflow_new returns -EINVAL when msk socket lock
> > isn't
> > held.
> >
> > Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> > ---
> > net/mptcp/bpf.c | 10 +++++++++-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/net/mptcp/bpf.c b/net/mptcp/bpf.c
> > index f9ba0a46a9f1..0563d3c6d9d3 100644
> > --- a/net/mptcp/bpf.c
> > +++ b/net/mptcp/bpf.c
> > @@ -232,12 +232,20 @@ bpf_iter_mptcp_subflow_new(struct
> > bpf_iter_mptcp_subflow *it,
> > struct mptcp_sock *msk)
> > {
> > struct bpf_iter_mptcp_subflow_kern *kit = (void *)it;
> > + struct sock *sk = (struct sock *)msk;
> > +
> > + BUILD_BUG_ON(sizeof(struct bpf_iter_mptcp_subflow_kern) >
> > + sizeof(struct bpf_iter_mptcp_subflow));
> > + BUILD_BUG_ON(__alignof__(struct
> > bpf_iter_mptcp_subflow_kern) !=
> > + __alignof__(struct bpf_iter_mptcp_subflow));
> >
> > kit->msk = msk;
> > if (!msk)
> > return -EINVAL;
> >
> > - msk_owned_by_me(msk);
> > + if (!sock_owned_by_user_nocheck(sk) &&
> > + !spin_is_locked(&sk->sk_lock.slock))
> > + return -EINVAL;
>
> Just to be sure, did you check it was always the case with the WIP
> scheduler and path-manager BPF programs you have?
Yes, I checked, BPF packet scheduler and BPF path manager are working
fine. Thanks for your other suggestions on this set, I have updated to
the new version v5.
-Geliang
>
> We don't want to be too restrictive. (Or we need different helpers)
>
> Cheers,
> Matt
next prev parent reply other threads:[~2024-12-11 3:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 8:47 [PATCH mptcp-next v4 0/5] Squash to "Add mptcp_subflow bpf_iter support" Geliang Tang
2024-12-09 8:47 ` [PATCH mptcp-next v4 1/5] mptcp: update bpf_mptcp_sock_from_subflow Geliang Tang
2024-12-10 11:43 ` Matthieu Baerts
2024-12-09 8:47 ` [PATCH mptcp-next v4 2/5] bpf: Allow use of skc_to_mptcp_sock in cg_sockopt Geliang Tang
2024-12-10 11:44 ` Matthieu Baerts
2024-12-09 8:47 ` [PATCH mptcp-next v4 3/5] Squash to "bpf: Register mptcp common kfunc set" Geliang Tang
2024-12-10 11:46 ` Matthieu Baerts
2024-12-09 8:47 ` [PATCH mptcp-next v4 4/5] Squash to "bpf: Add mptcp_subflow bpf_iter" Geliang Tang
2024-12-10 11:48 ` Matthieu Baerts
2024-12-11 3:42 ` Geliang Tang [this message]
2024-12-09 8:47 ` [PATCH mptcp-next v4 5/5] Squash to "selftests/bpf: Add mptcp_subflow bpf_iter subtest" Geliang Tang
2024-12-09 9:52 ` [PATCH mptcp-next v4 0/5] Squash to "Add mptcp_subflow bpf_iter support" 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=271ce327066dd6efe2e3ff793734a23279f26ca4.camel@kernel.org \
--to=geliang@kernel.org \
--cc=matttbe@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