From: patchwork-bot+netdevbpf@kernel.org
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: marcelo.leitner@gmail.com, lucien.xin@gmail.com,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v2] sctp: revalidate output stream after association connect wait
Date: Tue, 13 Oct 2026 08:40:04 +0000 [thread overview]
Message-ID: <179188080428.136048.15899244050224483580.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007035739.3472432-1-4ncienth@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 7 Oct 2026 12:57:39 +0900 you wrote:
> When message interleaving is enabled, the first send waits for association
> establishment before building its data chunks. The wait drops the socket
> lock, and handshake processing can reduce the output stream count to the
> peer-advertised inbound stream count. sctp_stream_init() then frees the
> extension of every removed stream.
>
> The sender resumes with the stream that it checked before the wait. If the
> peer removed that stream, sctp_outq_tail() later dereferences its NULL
> extension. Fatal-oops policies then panic the host.
>
> [...]
Here is the summary with links:
- [net,v2] sctp: revalidate output stream after association connect wait
https://git.kernel.org/netdev/net/c/b7ad72414c67
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-13 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 3:57 [PATCH net v2] sctp: revalidate output stream after association connect wait Daehyeon Ko
2026-10-08 15:57 ` netdev-bot+sashiko
2026-10-09 1:10 ` Xin Long
2026-10-09 1:12 ` Xin Long
2026-10-13 8:40 ` 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=179188080428.136048.15899244050224483580.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=4ncienth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 \
--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