All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Simon Horman <horms@kernel.org>, Florian Westphal <fw@strlen.de>,
	Dmytro Shytyi <dmytro@shytyi.net>,
	mptcp@lists.linux.dev, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Quanye Yang <quanyeyang@proton.me>,
	Petar Sakic <petar.sakic@ink.fish>,
	T S Rameshkumar <rameshkumar.t@phytecembedded.in>,
	Chris Mason <mason@kernel.org>,
	Mat Martineau <martineau@kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net 0/7] mptcp: misc fixes for v7.4-rc4
Date: Wed, 18 Nov 2026 23:05:24 +0100	[thread overview]
Message-ID: <869ba3ad-381e-41b1-adfe-2ef86fef5ad7@kernel.org> (raw)
In-Reply-To: <20261116-net-mptcp-misc-fixes-7-4-rc4-v1-0-bf7656de653e@kernel.org>

Hi Jakub, Paolo,

On 16/11/2026 23:06, Matthieu Baerts (NGI0) wrote:
> Here are some unrelated fixes:
> 
> - Patch 1: do not send data beyond the window announced by the peer. A
>   fix for v5.11.
> 
> - Patch 2: push pending data after a sendmsg copy fault. A fix for v6.1.
> 
> - Patches 3-6: with TFO, send the data written by a server before the
>   third ACK as soon as this ACK arrives, also in case of fallback to
>   TCP, even if the connection was shut down. Fixes for v6.2 and v5.19.
> 
> - Patch 7: after a fallback, fix the dummy mapping of overlapping
>   segments. A fix for v6.19.

TL;DR regarding the AI reviews: they are not blocking (to me): all "Low"
except on patch 6, but that's pre-existing and not a regression.

Note that patch 2 should have another Fixes tag (sent in my reply to
Clashiko). Sorry for that, Sashiko/Clashiko didn't notice that before.
If changing it when applying the patches is causing troubles, could you
please drop this patch 2/7 and apply the rest?

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


  parent reply	other threads:[~2026-11-18 22:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 22:06 [PATCH net 0/7] mptcp: misc fixes for v7.4-rc4 Matthieu Baerts (NGI0)
2026-11-16 22:06 ` [PATCH net 1/7] mptcp: do not use a raised snd_wnd for the send window Matthieu Baerts (NGI0)
2026-11-16 22:06 ` [PATCH net 2/7] mptcp: push pending data after a sendmsg copy fault Matthieu Baerts (NGI0)
2026-11-17 22:09   ` sashiko-bot
2026-11-17 22:29   ` netdev-bot+sashiko
2026-11-18 22:01     ` Matthieu Baerts
2026-11-16 22:06 ` [PATCH net 3/7] mptcp: use sk instead of casting msk in check_fully_established() Matthieu Baerts (NGI0)
2026-11-16 22:06 ` [PATCH net 4/7] mptcp: push queued data on passive TFO subflows becoming established Matthieu Baerts (NGI0)
2026-11-17 22:29   ` netdev-bot+sashiko
2026-11-18 22:02     ` Matthieu Baerts
2026-11-16 22:06 ` [PATCH net 5/7] mptcp: push queued data on subflows falling back at the handshake Matthieu Baerts (NGI0)
2026-11-17 22:09   ` sashiko-bot
2026-11-17 22:29   ` netdev-bot+sashiko
2026-11-18 22:02     ` Matthieu Baerts
2026-11-16 22:06 ` [PATCH net 6/7] mptcp: don't send a FIN before the pending data on fallback Matthieu Baerts (NGI0)
2026-11-17 22:09   ` sashiko-bot
2026-11-17 22:29   ` netdev-bot+sashiko
2026-11-18 22:03     ` Matthieu Baerts
2026-11-16 22:06 ` [PATCH net 7/7] mptcp: fix dummy mapping of overlapping segments Matthieu Baerts (NGI0)
2026-11-17 22:29   ` netdev-bot+sashiko
2026-11-18 22:04     ` Matthieu Baerts
2026-11-18 22:05 ` Matthieu Baerts [this message]
2026-11-20  2:32   ` [PATCH net 0/7] mptcp: misc fixes for v7.4-rc4 Jakub Kicinski
2026-11-20  8:50     ` Matthieu Baerts
2026-11-20  2:40 ` patchwork-bot+netdevbpf

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=869ba3ad-381e-41b1-adfe-2ef86fef5ad7@kernel.org \
    --to=matttbe@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dmytro@shytyi.net \
    --cc=edumazet@kernel.org \
    --cc=fw@strlen.de \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=mason@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petar.sakic@ink.fish \
    --cc=quanyeyang@proton.me \
    --cc=rameshkumar.t@phytecembedded.in \
    --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.