From: Matthieu Baerts <matttbe@kernel.org>
To: gregkh@linuxfoundation.org, jiayuan.chen@linux.dev, sashal@kernel.org
Cc: stable-commits@vger.kernel.org,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
jakub@cloudflare.com, martin.lau@kernel.org
Subject: Re: Patch "mptcp: Fix proto fallback detection with BPF" has been added to the 6.1-stable tree
Date: Fri, 28 Nov 2025 18:03:38 +0100 [thread overview]
Message-ID: <9e6ef98f-12eb-4608-aece-cf321e0a38d7@kernel.org> (raw)
In-Reply-To: <2025112711-frigidly-unruly-4a72@gregkh>
Hi Greg, Sasha, Jiayuan,
On 27/11/2025 14:41, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> mptcp: Fix proto fallback detection with BPF
>
> to the 6.1-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> mptcp-fix-proto-fallback-detection-with-bpf.patch
> and it can be found in the queue-6.1 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
@Sasha: thank you for having resolved the conflicts for this patch (and
many others related to MPTCP recently). Sadly, it is causing troubles.
@Greg/Sasha: is it possible to remove it from 6.1, 5.15 and 5.10 queues
please?
(The related patch in 6.6 and above is OK)
@Jiayuan: did you not specify you initially saw this issue on a v6.1
kernel? By chance, do you already have a fix for that version?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next parent reply other threads:[~2025-11-28 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025112711-frigidly-unruly-4a72@gregkh>
2025-11-28 17:03 ` Matthieu Baerts [this message]
2025-11-29 20:57 ` Patch "mptcp: Fix proto fallback detection with BPF" has been added to the 6.1-stable tree Sasha Levin
2025-11-30 3:09 ` Jiayuan Chen
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=9e6ef98f-12eb-4608-aece-cf321e0a38d7@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=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
--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