From: Matthieu Baerts <matttbe@kernel.org>
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: MPTCP Upstream <mptcp@lists.linux.dev>,
Martin KaFai Lau <martin.lau@kernel.org>,
Jakub Sitnicki <jakub@cloudflare.com>,
stable@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 6.1.y] mptcp: Fix proto fallback detection with BPF
Date: Mon, 1 Dec 2025 12:23:56 +0100 [thread overview]
Message-ID: <768dd161-bc91-4809-8ee0-3ce9d172c01c@kernel.org> (raw)
In-Reply-To: <e6ec12b0a9a3e0bc4db370b3fb6647f7127f4a04@linux.dev>
Hi Jiayuan,
On 01/12/2025 12:15, Jiayuan Chen wrote:
> December 1, 2025 at 18:45, "Matthieu Baerts (NGI0)" <matttbe@kernel.org mailto:matttbe@kernel.org?to=%22Matthieu%20Baerts%20(NGI0)%22%20%3Cmatttbe%40kernel.org%3E > wrote:
>
>
>>
>> From: Jiayuan Chen <jiayuan.chen@linux.dev>
>>
>> commit c77b3b79a92e3345aa1ee296180d1af4e7031f8f upstream.
(...)
> Thank you, Matthieu. I’ve tested the patch and confirmed it resolves the issue.
Thank you for having checked! Then I will also send the same patch for
v5.15 and v5.10.
Note: regarding your other patch fbade4bd08ba ("mptcp: Disallow MPTCP
subflows from sockmap"): it cannot be applied on v5.10. I have a draft,
but the modifications have to be done in sockmap code, not in MPTCP
side, and I don't want to introduce regressions for "normal" TCP sockmap
use. By chance, are you also able to test that one on a v5.10 kernel?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-12-01 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025112444-entangled-winking-ac86@gregkh>
2025-12-01 10:45 ` [PATCH 6.1.y] mptcp: Fix proto fallback detection with BPF Matthieu Baerts (NGI0)
2025-12-01 11:15 ` Jiayuan Chen
2025-12-01 11:23 ` Matthieu Baerts [this message]
2025-12-02 16:02 ` Patch "mptcp: Fix proto fallback detection with BPF" has been added to the 6.1-stable tree gregkh
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=768dd161-bc91-4809-8ee0-3ce9d172c01c@kernel.org \
--to=matttbe@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jakub@cloudflare.com \
--cc=jiayuan.chen@linux.dev \
--cc=martin.lau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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