From: patchwork-bot+netdevbpf@kernel.org
To: Jun Yang <juny24602@gmail.com>
Cc: marcelo.leitner@gmail.com, lucien.xin@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, david.lee@trailofbits.com,
kylebot@openai.com
Subject: Re: [PATCH net v4 0/2] sctp: re-point retained control chunks on association migration
Date: Fri, 16 Oct 2026 00:10:05 +0000 [thread overview]
Message-ID: <179210940527.4168191.7880710417469627845.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009074244.3718-1-juny24602@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Oct 2026 15:42:30 +0800 you wrote:
> This series fixes ownership of retained SCTP control chunks during socket
> migration. Patch 1 carries David Lee's shared-key prerequisite.
>
> Changes since v3 [1], following Xin Long's review:
> - Add David Lee's and the forwarding submitter's sign-offs to patch 1.
> - Restore sctp_process_tx_chunk() to skip duplicate visits.
> - Preserve a control chunk's existing shared key across migration.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] sctp: hold shkey across socket migration
https://git.kernel.org/netdev/net/c/ad1320865b18
- [net,v4,2/2] sctp: re-point retained control chunks on association migration
https://git.kernel.org/netdev/net/c/52ffeaa358d1
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-10-16 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 7:42 [PATCH net v4 0/2] sctp: re-point retained control chunks on association migration Jun Yang
2026-10-09 7:42 ` [PATCH net v4 1/2] sctp: hold shkey across socket migration Jun Yang
2026-10-09 7:42 ` [PATCH net v4 2/2] sctp: re-point retained control chunks on association migration Jun Yang
2026-10-12 17:49 ` Xin Long
2026-10-16 0:10 ` 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=179210940527.4168191.7880710417469627845.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=david.lee@trailofbits.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=juny24602@gmail.com \
--cc=kuba@kernel.org \
--cc=kylebot@openai.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.