From: Sasha Levin <sashal@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: gregkh@linuxfoundation.org, stable-commits@vger.kernel.org,
geliang@kernel.org, kuba@kernel.org, martineau@kernel.org,
pabeni@redhat.com,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: Patch "mptcp: drop bogus optimization in __mptcp_check_push()" has been added to the 5.15-stable tree
Date: Thu, 13 Nov 2025 10:47:41 -0500 [thread overview]
Message-ID: <aRX9nX8aN5iZ4IpL@laps> (raw)
In-Reply-To: <48bbe998-982c-4dbd-b261-83c076ebcb7a@kernel.org>
On Thu, Nov 13, 2025 at 04:19:56PM +0100, Matthieu Baerts wrote:
>Hi Greg, Sasha,
>
>On 03/11/2025 02:38, gregkh@linuxfoundation.org wrote:
>>
>> This is a note to let you know that I've just added the patch titled
>>
>> mptcp: drop bogus optimization in __mptcp_check_push()
>>
>> to the 5.15-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-drop-bogus-optimization-in-__mptcp_check_push.patch
>> and it can be found in the queue-5.15 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.
>
>Can you please drop this patch from v5.15? It looks like it is causing
>some issues with MP_PRIO tests. I think that's because back then, the
>path is selected differently, with the use of 'msk->last_snd' which will
>bypass some decisions to where to send the next data.
>
>I will try to check if another version of this patch is needed for v5.15.
Sure, now dropped from 5.15.
--
Thanks,
Sasha
prev parent reply other threads:[~2025-11-13 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025110310-scapegoat-magnetic-3cf8@gregkh>
2025-11-13 15:19 ` Patch "mptcp: drop bogus optimization in __mptcp_check_push()" has been added to the 5.15-stable tree Matthieu Baerts
2025-11-13 15:47 ` Sasha Levin [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=aRX9nX8aN5iZ4IpL@laps \
--to=sashal@kernel.org \
--cc=geliang@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
--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