From: Jun Yang <juny24602@gmail.com>
To: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Xin Long <lucien.xin@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
David Lee <david.lee@trailofbits.com>,
Kyle Zeng <kylebot@openai.com>
Subject: [PATCH net v4 0/2] sctp: re-point retained control chunks on association migration
Date: Fri, 9 Oct 2026 15:42:30 +0800 [thread overview]
Message-ID: <20261009074244.3718-1-juny24602@gmail.com> (raw)
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.
[1] https://lore.kernel.org/netdev/20260926100359.78731-1-juny24602@gmail.com/
David Lee (1):
sctp: hold shkey across socket migration
Jun Yang (1):
sctp: re-point retained control chunks on association migration
include/net/sctp/sm.h | 1 +
net/sctp/sm_make_chunk.c | 5 +++--
net/sctp/socket.c | 57 +++++++++++++++++++++++++++++++++++++++---------
3 files changed, 51 insertions(+), 12 deletions(-)
base-commit: a7bfaba4823e3c165bb2004c74eff7c096672bc7
next reply other threads:[~2026-10-09 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 7:42 Jun Yang [this message]
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
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=20261009074244.3718-1-juny24602@gmail.com \
--to=juny24602@gmail.com \
--cc=davem@davemloft.net \
--cc=david.lee@trailofbits.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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.