From: patchwork-bot+netdevbpf@kernel.org
To: Michal Luczaj <mhal@rbox.co>
Cc: sgarzare@redhat.com, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] vsock/test: Extend transport change null-ptr-deref test
Date: Wed, 26 Nov 2025 03:20:29 +0000 [thread overview]
Message-ID: <176412722900.1502845.12794410692488163252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251123-vsock_test-linger-lockdep-warn-v1-1-4b1edf9d8cdc@rbox.co>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 23 Nov 2025 22:43:59 +0100 you wrote:
> syzkaller reported a lockdep lock order inversion warning[1] due to
> commit 687aa0c5581b ("vsock: Fix transport_* TOCTOU"). This was fixed in
> commit f7c877e75352 ("vsock: fix lock inversion in
> vsock_assign_transport()").
>
> Redo syzkaller's repro by piggybacking on a somewhat related test
> implemented in commit 3a764d93385c ("vsock/test: Add test for null ptr
> deref when transport changes").
>
> [...]
Here is the summary with links:
- [net-next] vsock/test: Extend transport change null-ptr-deref test
https://git.kernel.org/netdev/net-next/c/b796632fc83c
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-11-26 3:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 21:43 [PATCH net-next] vsock/test: Extend transport change null-ptr-deref test Michal Luczaj
2025-11-24 11:41 ` Stefano Garzarella
2025-11-26 3:20 ` 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=176412722900.1502845.12794410692488163252.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.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