netdev - Re: [PATCH net] rxrpc: Fix call timer start racing with call destruction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <164872381082.31367.2236478294404070151.git-patchwork-notify@kernel.org>
Date:   Thu, 31 Mar 2022 10:50:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     David Howells <dhowells@...hat.com>
Cc:     netdev@...r.kernel.org, marc.dionne@...istor.com,
        linux-afs@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] rxrpc: Fix call timer start racing with call destruction

Hello:

This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@...hat.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