All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: kuba@kernel.org, martineau@kernel.org, pabeni@redhat.com,
	sashal@kernel.org, stable-commits@vger.kernel.org,
	MPTCP Linux <mptcp@lists.linux.dev>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Patch "mptcp: move the whole rx path under msk socket lock protection" has been added to the 6.12-stable tree
Date: Tue, 4 Nov 2025 08:52:57 +0900	[thread overview]
Message-ID: <2025110444-rendering-exhale-0bd8@gregkh> (raw)
In-Reply-To: <bbe84711-95b2-4257-9f01-560b4473a3da@kernel.org>

On Mon, Nov 03, 2025 at 08:13:30PM +0100, Matthieu Baerts wrote:
> Hi Greg, Sasha,
> 
> On 03/11/2025 02:29, gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     mptcp: move the whole rx path under msk socket lock protection
> > 
> > to the 6.12-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-move-the-whole-rx-path-under-msk-socket-lock-protection.patch
> > and it can be found in the queue-6.12 subdirectory.
> 
> Thank you for the backport!
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> Please drop this patch from the 6.12-stable tree: it causes troubles in
> the MPTCP selftests: MPTCP to TCP connections timeout when MSG_PEEK is
> used. Likely a dependence is missing, and it might be better to keep
> only the last patch, and resolve conflicts. I will check that ASAP.
> 
> In the meantime, can you then drop this patch and the ones that are
> linked to it please?
> 
> queue-6.12/mptcp-cleanup-mem-accounting.patch
> queue-6.12/mptcp-fix-msg_peek-stream-corruption.patch
> queue-6.12/mptcp-move-the-whole-rx-path-under-msk-socket-lock-protection.patch
> queue-6.12/mptcp-leverage-skb-deferral-free.patch

all now dropped, thanks.

greg k-h

      reply	other threads:[~2025-11-03 23:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025110351-praising-bounce-a06b@gregkh>
2025-11-03 19:13 ` Patch "mptcp: move the whole rx path under msk socket lock protection" has been added to the 6.12-stable tree Matthieu Baerts
2025-11-03 23:52   ` Greg KH [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=2025110444-rendering-exhale-0bd8@gregkh \
    --to=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.