From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rxrpc: Fix call timer start racing with call destruction
Date: Thu, 31 Mar 2022 10:50:10 +0000 [thread overview]
Message-ID: <164872381082.31367.2236478294404070151.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <164865115696.2943015.11097991776647323586.stgit@warthog.procyon.org.uk>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 30 Mar 2022 15:39:16 +0100 you wrote:
> The rxrpc_call struct has a timer used to handle various timed events
> relating to a call. This timer can get started from the packet input
> routines that are run in softirq mode with just the RCU read lock held.
> Unfortunately, because only the RCU read lock is held - and neither ref or
> other lock is taken - the call can start getting destroyed at the same time
> a packet comes in addressed to that call. This causes the timer - which
> was already stopped - to get restarted. Later, the timer dispatch code may
> then oops if the timer got deallocated first.
>
> [...]
Here is the summary with links:
- [net] rxrpc: Fix call timer start racing with call destruction
https://git.kernel.org/netdev/net/c/4a7f62f91933
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:[~2022-03-31 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 14:39 [PATCH net] rxrpc: Fix call timer start racing with call destruction David Howells
2022-03-31 10: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=164872381082.31367.2236478294404070151.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.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