MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, 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: Wed, 5 Mar 2025 16:31:20 +0100	[thread overview]
Message-ID: <3946fafa-272f-4a0e-8461-e8b17f8283b2@kernel.org> (raw)
In-Reply-To: <cover.1740368110.git.tanggeliang@kylinos.cn>

Hi Geliang, Mat,

On 24/02/2025 04:37, 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.

Thank you for the patches and the reviews!

Now in our tree:

New patches for t/upstream:
- fe0c24467a00: "squashed" patch 1/5 in "bpf: Extend
bpf_skc_to_mptcp_sock to MPTCP sock"
- 83bb4052ab8a: "squashed" patch 2/5 in "bpf: Allow use of
skc_to_mptcp_sock in cg_sockopt"
- dd8797c750fe: "squashed" patch 3/5 in "bpf: Add mptcp_subflow bpf_iter"
- a5e732a840e2: "squashed" my patch in "bpf: Add mptcp_subflow bpf_iter"
- 23094de26cb5: "squashed" (with conflicts) patch 4/5 in "bpf: Acquire
and release mptcp socket"
- 5a1d91403efd: "squashed" patch 5/5 in "selftests/bpf: Add
mptcp_subflow bpf_iter subtest"
- 29cc864a2cc6: tg:msg: update after the recent squash-to patch
- da6054a670da: conflict in t/mptcp-add-sched_data-helpers-2
- 401780491d45: conflict in t/mptcp-add-bpf_mptcp_sched_ops
- Results: e1315f2b7271..bf7e42dbc2fa (export)

Tests are now in progress:

- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/0447c3073f646734cffeec271b1a6b03a53103ef/checks

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  parent reply	other threads:[~2025-03-05 15:31 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 [this message]
2025-03-06  1:50 ` Geliang Tang
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=3946fafa-272f-4a0e-8461-e8b17f8283b2@kernel.org \
    --to=matttbe@kernel.org \
    --cc=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