From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, marcelo.leitner@gmail.com,
yuantan098@gmail.com, yifanwucs@gmail.com,
tomapufckgml@gmail.com, zcliangcn@gmail.com, bird@lzu.edu.cn,
xuyq21@lenovo.com, n05ec@lzu.edu.cn
Subject: Re: [PATCH net] sctp: purge outqueue on stale COOKIE-ECHO handling
Date: Thu, 04 Jun 2026 16:20:19 +0000 [thread overview]
Message-ID: <178059001964.2502005.1832706734432444090.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <94318159b9052907a6cbb7256aee8b5f8dfbfccb.1780510304.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 3 Jun 2026 14:11:44 -0400 you wrote:
> sctp_stream_update() is only invoked when the association is moved into
> COOKIE_WAIT during association setup/reconfiguration. In this path, the
> outbound stream scheduler state (stream->out_curr) is expected to be
> clean, since no user data should have been transmitted yet unless the
> state machine has already partially progressed.
>
> However, a corner case exists in sctp_sf_do_5_2_6_stale(): when a
> Stale Cookie ERROR is received, the association is rolled back from
> COOKIE_ECHOED to COOKIE_WAIT. In this scenario, user data may already
> have been queued and even bundled with the COOKIE-ECHO chunk.
>
> [...]
Here is the summary with links:
- [net] sctp: purge outqueue on stale COOKIE-ECHO handling
https://git.kernel.org/netdev/net/c/e374b22e9b07
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-06-04 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 18:11 [PATCH net] sctp: purge outqueue on stale COOKIE-ECHO handling Xin Long
2026-06-04 16:20 ` 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=178059001964.2502005.1832706734432444090.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bird@lzu.edu.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=n05ec@lzu.edu.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tomapufckgml@gmail.com \
--cc=xuyq21@lenovo.com \
--cc=yifanwucs@gmail.com \
--cc=yuantan098@gmail.com \
--cc=zcliangcn@gmail.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