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,
xietangxin@h-partners.com, david.laight.linux@gmail.com
Subject: Re: [PATCH net] sctp: hold asoc or transport before mod_timer() in timer handlers
Date: Wed, 23 Sep 2026 02:00:10 +0000 [thread overview]
Message-ID: <179012881076.173471.14609989532981341601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c31b5e3ee2b7274e804f5eba2f21e2412e7eef7a.1790013825.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Sep 2026 14:03:45 -0400 you wrote:
> Take the association or transport reference before rearming a timer in the
> timer handlers.
>
> The existing code calls mod_timer() before taking the reference needed by
> the rearmed timer without holding the sock lock. This creates a race with
> timer cleanup: if the timer is deleted after mod_timer() returns but before
> the reference is taken, the cleanup path can drop the timer's reference and
> destroy the transport or association. The timer handler then takes a
> reference on the already freed object and eventually drops it, causing a
> refcount underflow.
>
> [...]
Here is the summary with links:
- [net] sctp: hold asoc or transport before mod_timer() in timer handlers
https://git.kernel.org/netdev/net/c/cae23ae3f788
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-09-23 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 18:03 [PATCH net] sctp: hold asoc or transport before mod_timer() in timer handlers Xin Long
2026-09-23 2:00 ` 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=179012881076.173471.14609989532981341601.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xietangxin@h-partners.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