MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net 0/3] mptcp: avoid uninitialised read with MPJ with SYN cookies
Date: Fri, 21 Aug 2026 08:32:05 +0200	[thread overview]
Message-ID: <4a6a4ef8-4b3e-4717-9dfe-4f6d7fc14b77@kernel.org> (raw)
In-Reply-To: <0234c8e501a033d22733138b77ce19270fed7401.camel@kernel.org>

Hi Geliang,

On 21/08/2026 07:37, Geliang Tang wrote:
> Hi Matt,
> 
> On Tue, 2026-08-18 at 19:20 +0000, MPTCP CI wrote:
>> Hi Matthieu,
>>
>> Thank you for your modifications, that's great!
>>
>> Our CI did some validations and here is its report:
>>
>> - KVM Validation: normal (except selftest_mptcp_join): Success! ✅
>> - KVM Validation: normal (only selftest_mptcp_join): Success! ✅
>> - KVM Validation: debug (except selftest_mptcp_join): Success! ✅
>> - KVM Validation: debug (only selftest_mptcp_join): Unstable: 1
>> failed test(s): selftest_mptcp_join ⚠️ 
>> - KVM Validation: btf-normal (only bpftest_all): Success! ✅
>> - KVM Validation: btf-debug (only bpftest_all): Success! ✅
> 
> This series looks good to me!

Thank you for the review!

New patches for t/upstream-net and t/upstream:
- cba636a2dcab: mptcp: syncookies: remember the request backup flag
- 413a21edd334: mptcp: subflow: no need to copy thmac during ulp_clone
- Results: eeb8d1d44a74..6bb246941708 (export-net)
- Results: 41733b9765ba..aa4bae9bfb46 (export)

Tests are now in progress:

- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/d9e7fa174e7b3c63fafb99573c8c7e1a8ce53b06/checks

New patches for t/upstream:
- 631307ac3350: mptcp: remove thmac from subflow ctx
- Results: aa4bae9bfb46..2f5abecdd265 (export)

Tests are now in progress:

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

> nit: You could squash patch 2 into patch 3 if you want, but totally up
> to you.
I didn't: the 2nd patch is -net material, while the 3rd one is for -next.

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


      reply	other threads:[~2026-08-21  6:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 17:55 [PATCH mptcp-net 0/3] mptcp: avoid uninitialised read with MPJ with SYN cookies Matthieu Baerts (NGI0)
2026-08-18 17:55 ` [PATCH mptcp-net 1/3] mptcp: syncookies: remember the request backup flag Matthieu Baerts (NGI0)
2026-08-18 17:55 ` [PATCH mptcp-net 2/3] mptcp: subflow: no need to copy thmac during ulp_clone Matthieu Baerts (NGI0)
2026-08-21  6:03   ` Matthieu Baerts
2026-08-21  6:06     ` Matthieu Baerts
2026-08-18 17:55 ` [PATCH next mptcp-net 3/3] mptcp: remove thmac from subflow ctx Matthieu Baerts (NGI0)
2026-08-19  9:56   ` Geliang Tang
2026-08-19 10:02     ` Matthieu Baerts
2026-08-21  5:33       ` Geliang Tang
2026-08-18 19:20 ` [PATCH mptcp-net 0/3] mptcp: avoid uninitialised read with MPJ with SYN cookies MPTCP CI
2026-08-21  5:37   ` Geliang Tang
2026-08-21  6:32     ` Matthieu Baerts [this message]

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=4a6a4ef8-4b3e-4717-9dfe-4f6d7fc14b77@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox