Re: [PATCH resend mptcp-net 0/4] mptcp: a few fixes

Matthieu Baerts <[email protected]>
Newsgroups dev.linux.lists.mptcp
Organization NGI0 Core
Message-ID <[email protected]>
Hi Paolo, Geliang,

On 14/08/2026 15:38, Paolo Abeni wrote:
> This is mostly a follow-up to the recent OoO queue pruning series.
> Explicitly targeting net as we have already a lot of patches pending for
> net-next, and no need to rush IMHO.
> 
> First 2 patches addresses explicit comments from sashiko, 3rd one is a
> somewhat unrelated cleanup I stumbled upon while implementing patch 4.
> 
> The last patch fixes another thing implided by sashiko while reviewing
> the mentioned series.
Now in our tree:

New patches for t/upstream-net and t/upstream:
- 6280287c0ef2: mptcp: being below memory limit is a likely() condition
- e66f97348c99: mptcp: avoid pruning for OoW data
- cdd6976ab76f: mptcp: remove unneeded READ_ONCE() annotation
- 285d84ee4b60: mptcp: do not reschedule the RTX timer for fallback sockets
- Results: 6bb246941708..70d6bffa3696 (export-net)
- Results: 2f5abecdd265..0afd98c500bf (export)

Tests are now in progress:

- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/71a020c17359779f858419627d7933171dafee9a/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/8ff26825a673fb98ff86413940a0254088cf0bd3/checks

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.