From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, fw@strlen.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org,
arinc.unal@arinc9.com,
syzbot+455d38ecd5f655fc45cf@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2 00/15] mptcp: more fixes for the in-kernel PM
Date: Thu, 29 Aug 2024 09:00:45 +0000 [thread overview]
Message-ID: <172492204527.1873855.649951306821371963.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240828-net-mptcp-more-pm-fix-v2-0-7f11b283fff7@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 28 Aug 2024 08:14:23 +0200 you wrote:
> Here is a new batch of fixes for the MPTCP in-kernel path-manager:
>
> Patch 1 ensures the address ID is set to 0 when the path-manager sends
> an ADD_ADDR for the address of the initial subflow. The same fix is
> applied when a new subflow is created re-using this special address. A
> fix for v6.0.
>
> [...]
Here is the summary with links:
- [net,v2,01/15] mptcp: pm: reuse ID 0 after delete and re-add
https://git.kernel.org/netdev/net/c/8b8ed1b429f8
- [net,v2,02/15] mptcp: pm: fix RM_ADDR ID for the initial subflow
https://git.kernel.org/netdev/net/c/87b5896f3f78
- [net,v2,03/15] selftests: mptcp: join: check removing ID 0 endpoint
https://git.kernel.org/netdev/net/c/5f94b08c0012
- [net,v2,04/15] mptcp: pm: send ACK on an active subflow
https://git.kernel.org/netdev/net/c/c07cc3ed895f
- [net,v2,05/15] mptcp: pm: skip connecting to already established sf
https://git.kernel.org/netdev/net/c/bc19ff57637f
- [net,v2,06/15] mptcp: pm: reset MPC endp ID when re-added
https://git.kernel.org/netdev/net/c/dce1c6d1e925
- [net,v2,07/15] selftests: mptcp: join: check re-adding init endp with != id
https://git.kernel.org/netdev/net/c/1c2326fcae4f
- [net,v2,08/15] selftests: mptcp: join: no extra msg if no counter
https://git.kernel.org/netdev/net/c/76a2d8394cc1
- [net,v2,09/15] mptcp: pm: do not remove already closed subflows
https://git.kernel.org/netdev/net/c/58e1b66b4e4b
- [net,v2,10/15] mptcp: pm: fix ID 0 endp usage after multiple re-creations
https://git.kernel.org/netdev/net/c/9366922adc6a
- [net,v2,11/15] selftests: mptcp: join: check re-re-adding ID 0 endp
https://git.kernel.org/netdev/net/c/d397d7246c11
- [net,v2,12/15] mptcp: avoid duplicated SUB_CLOSED events
https://git.kernel.org/netdev/net/c/d82809b6c5f2
- [net,v2,13/15] selftests: mptcp: join: validate event numbers
https://git.kernel.org/netdev/net/c/20ccc7c5f7a3
- [net,v2,14/15] mptcp: pm: ADD_ADDR 0 is not a new address
https://git.kernel.org/netdev/net/c/57f86203b41c
- [net,v2,15/15] selftests: mptcp: join: check re-re-adding ID 0 signal
https://git.kernel.org/netdev/net/c/f18fa2abf810
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:[~2024-08-29 9:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 6:14 [PATCH net v2 00/15] mptcp: more fixes for the in-kernel PM Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 01/15] mptcp: pm: reuse ID 0 after delete and re-add Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 02/15] mptcp: pm: fix RM_ADDR ID for the initial subflow Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 03/15] selftests: mptcp: join: check removing ID 0 endpoint Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 04/15] mptcp: pm: send ACK on an active subflow Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 05/15] mptcp: pm: skip connecting to already established sf Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 06/15] mptcp: pm: reset MPC endp ID when re-added Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 07/15] selftests: mptcp: join: check re-adding init endp with != id Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 08/15] selftests: mptcp: join: no extra msg if no counter Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 09/15] mptcp: pm: do not remove already closed subflows Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 10/15] mptcp: pm: fix ID 0 endp usage after multiple re-creations Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 11/15] selftests: mptcp: join: check re-re-adding ID 0 endp Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 12/15] mptcp: avoid duplicated SUB_CLOSED events Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 13/15] selftests: mptcp: join: validate event numbers Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 14/15] mptcp: pm: ADD_ADDR 0 is not a new address Matthieu Baerts (NGI0)
2024-08-28 6:14 ` [PATCH net v2 15/15] selftests: mptcp: join: check re-re-adding ID 0 signal Matthieu Baerts (NGI0)
2024-08-29 9:00 ` 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=172492204527.1873855.649951306821371963.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=geliang@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 \
--cc=syzbot+455d38ecd5f655fc45cf@syzkaller.appspotmail.com \
/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