From: patchwork-bot+netdevbpf@kernel.org
To: Jun Yang <1753810072@qq.com>
Cc: netdev@vger.kernel.org, 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, linux-kernel@vger.kernel.org,
junvyyang@tencent.com, stable@kernel.org
Subject: Re: [PATCH net v3] sctp: don't free the ASCONF's own transport in DEL-IP processing
Date: Thu, 23 Jul 2026 17:40:07 +0000 [thread overview]
Message-ID: <178482840779.2802214.4496095044368060549.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_73762ED1DF08CC9D5F5F61954B01350CFE0A@qq.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 21 Jul 2026 21:14:05 +0800 you wrote:
> From: Jun Yang <junvyyang@tencent.com>
>
> sctp_process_asconf() caches the transport the ASCONF chunk is processed
> against in asconf->transport (== chunk->transport, set once in sctp_rcv()).
> For an ASCONF located through its Address Parameter by
> __sctp_rcv_asconf_lookup(), that cached transport corresponds to the
> Address Parameter, which need not be the packet's source address.
>
> [...]
Here is the summary with links:
- [net,v3] sctp: don't free the ASCONF's own transport in DEL-IP processing
https://git.kernel.org/netdev/net/c/9b2854f86f0b
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-07-23 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 13:14 [PATCH net v3] sctp: don't free the ASCONF's own transport in DEL-IP processing Jun Yang
2026-07-23 14:29 ` Jakub Kicinski
2026-07-23 15:33 ` Xin Long
2026-07-23 17:35 ` Jakub Kicinski
2026-07-23 17: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=178482840779.2802214.4496095044368060549.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=1753810072@qq.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=junvyyang@tencent.com \
--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@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