From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, horms@kernel.org, pabeni@redhat.com,
linux-kernel@vger.kernel.org, kuba@kernel.org,
virtualization@lists.linux.dev, mhal@rbox.co,
edumazet@google.com, davem@davemloft.net,
syzbot+10e35716f8e4929681fa@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH net] vsock: fix lock inversion in vsock_assign_transport()
Date: Thu, 23 Oct 2025 14:10:40 +0000 [thread overview]
Message-ID: <176122864026.3096909.17516600367441031200.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251021121718.137668-1-sgarzare@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 21 Oct 2025 14:17:18 +0200 you wrote:
> From: Stefano Garzarella <sgarzare@redhat.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
prev parent reply other threads:[~2025-10-23 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 12:17 [PATCH net] vsock: fix lock inversion in vsock_assign_transport() Stefano Garzarella
2025-10-23 14:10 ` 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=176122864026.3096909.17516600367441031200.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+10e35716f8e4929681fa@syzkaller.appspotmail.com \
--cc=virtualization@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).