From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: martineau@kernel.org, geliang@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, cpaasch@openai.com, netdev@vger.kernel.org,
mptcp@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 00/11] mptcp: pm: misc. fixes for v7.1-rc3
Date: Thu, 07 May 2026 01:30:23 +0000 [thread overview]
Message-ID: <177811742303.3291094.15207378562960024252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260505-net-mptcp-pm-fixes-7-1-rc3-v1-0-fca8091060a4@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 05 May 2026 17:00:48 +0200 you wrote:
> Here are various fixes, mainly related to ADD_ADDRs:
>
> - Patch 1: save ADD_ADDR for rtx with ID0 when needed. A fix for v6.1.
>
> - Patch 2: remove unneeded exception for ID 0. A fix for v5.10.
>
> - Patches 3-5: fix potential data-race and leaks during ADD_ADDR rtx. A
> fix for v5.10.
>
> [...]
Here is the summary with links:
- [net,01/11] mptcp: pm: kernel: correctly retransmit ADD_ADDR ID 0
https://git.kernel.org/netdev/net/c/b12014d2d36e
- [net,02/11] mptcp: pm: ADD_ADDR rtx: allow ID 0
https://git.kernel.org/netdev/net/c/03f324f3f1f7
- [net,03/11] mptcp: pm: ADD_ADDR rtx: fix potential data-race
https://git.kernel.org/netdev/net/c/5cd6e0ad79d2
- [net,04/11] mptcp: pm: ADD_ADDR rtx: always decrease sk refcount
https://git.kernel.org/netdev/net/c/9634cb35af17
- [net,05/11] mptcp: pm: ADD_ADDR rtx: free sk if last
https://git.kernel.org/netdev/net/c/b7b9a4615697
- [net,06/11] mptcp: pm: ADD_ADDR rtx: resched blocked ADD_ADDR quicker
https://git.kernel.org/netdev/net/c/3cf12492891c
- [net,07/11] mptcp: pm: ADD_ADDR rtx: skip inactive subflows
https://git.kernel.org/netdev/net/c/c6d395e2de13
- [net,08/11] mptcp: pm: ADD_ADDR rtx: return early if no retrans
https://git.kernel.org/netdev/net/c/62a9b19dce77
- [net,09/11] mptcp: pm: prio: skip closed subflows
https://git.kernel.org/netdev/net/c/166b78344031
- [net,10/11] selftests: mptcp: check output: catch cmd errors
https://git.kernel.org/netdev/net/c/65db7b27b90e
- [net,11/11] selftests: mptcp: pm: restrict 'unknown' check to pm_nl_ctl
https://git.kernel.org/netdev/net/c/53705ddfa184
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-07 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 15:00 [PATCH net 00/11] mptcp: pm: misc. fixes for v7.1-rc3 Matthieu Baerts (NGI0)
2026-05-05 15:00 ` [PATCH net 10/11] selftests: mptcp: check output: catch cmd errors Matthieu Baerts (NGI0)
2026-05-05 15:00 ` [PATCH net 11/11] selftests: mptcp: pm: restrict 'unknown' check to pm_nl_ctl Matthieu Baerts (NGI0)
2026-05-07 1:30 ` patchwork-bot+netdevbpf [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=177811742303.3291094.15207378562960024252.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cpaasch@openai.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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