[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<176122864026.3096909.17516600367441031200.git-patchwork-notify@kernel.org>
Date: Thu, 23 Oct 2025 14:10:40 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: netdev@...r.kernel.org, horms@...nel.org, pabeni@...hat.com,
linux-kernel@...r.kernel.org, kuba@...nel.org,
virtualization@...ts.linux.dev, mhal@...x.co, edumazet@...gle.com,
davem@...emloft.net, syzbot+10e35716f8e4929681fa@...kaller.appspotmail.com,
stable@...r.kernel.org
Subject: Re: [PATCH net] vsock: fix lock inversion in vsock_assign_transport()
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Tue, 21 Oct 2025 14:17:18 +0200 you wrote:
> From: Stefano Garzarella <sgarzare@...hat.com>
>
> Syzbot reported a potential lock inversion deadlock between
> vsock_register_mutex and sk_lock-AF_VSOCK when vsock_linger() is called.
>
> The issue was introduced by commit 687aa0c5581b ("vsock: Fix
> transport_* TOCTOU") which added vsock_register_mutex locking in
> vsock_assign_transport() around the transport->release() call, that can
> call vsock_linger(). vsock_assign_transport() can be called with sk_lock
> held. vsock_linger() calls sk_wait_event() that temporarily releases and
> re-acquires sk_lock. During this window, if another thread hold
> vsock_register_mutex while trying to acquire sk_lock, a circular
> dependency is created.
>
> [...]
Here is the summary with links:
- [net] vsock: fix lock inversion in vsock_assign_transport()
https://git.kernel.org/netdev/net/c/f7c877e75352
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists