From: patchwork-bot+netdevbpf@kernel.org
To: Zhenghang Xiao <kipreyyy@gmail.com>
Cc: marcelo.leitner@gmail.com, lucien.xin@gmail.com,
linux-sctp@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net] sctp: fix race between sctp_wait_for_connect and peeloff
Date: Thu, 28 May 2026 23:50:06 +0000 [thread overview]
Message-ID: <178001220615.1560944.11263521787130041641.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260527032411.60959-1-kipreyyy@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 May 2026 11:24:11 +0800 you wrote:
> sctp_wait_for_connect() drops and re-acquires the socket lock while
> waiting for the association to reach ESTABLISHED state. During this
> window, another thread can peeloff the association to a new socket via
> getsockopt(SCTP_SOCKOPT_PEELOFF), changing asoc->base.sk. After
> re-acquiring the old socket lock, sctp_wait_for_connect() returns
> success without noticing the migration — the caller then accesses
> the association under the wrong lock in sctp_datamsg_from_user().
>
> [...]
Here is the summary with links:
- [net] sctp: fix race between sctp_wait_for_connect and peeloff
https://git.kernel.org/netdev/net/c/f14fe6395a8b
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-28 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 3:24 [PATCH net] sctp: fix race between sctp_wait_for_connect and peeloff Zhenghang Xiao
2026-05-28 13:41 ` Xin Long
2026-05-28 23:50 ` 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=178001220615.1560944.11263521787130041641.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=kipreyyy@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@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