From: patchwork-bot+netdevbpf@kernel.org
To: Michal Luczaj <mhal@rbox.co>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
stefanha@redhat.com, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4 0/3] vsock: Fix transport_{h2g,g2h,dgram,local} TOCTOU issues
Date: Tue, 08 Jul 2025 16:00:11 +0000 [thread overview]
Message-ID: <175199041100.4117860.14540554652345521469.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250703-vsock-transports-toctou-v4-0-98f0eb530747@rbox.co>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 03 Jul 2025 17:18:17 +0200 you wrote:
> transport_{h2g,g2h,dgram,local} may become NULL on vsock_core_unregister().
> Make sure a poorly timed `rmmod transport` won't lead to a NULL/stale
> pointer dereference.
>
> Note that these oopses are pretty unlikely to happen in the wild. Splats
> were collected after sprinkling kernel with mdelay()s.
>
> [...]
Here is the summary with links:
- [net,v4,1/3] vsock: Fix transport_{g2h,h2g} TOCTOU
https://git.kernel.org/netdev/net/c/209fd720838a
- [net,v4,2/3] vsock: Fix transport_* TOCTOU
https://git.kernel.org/netdev/net/c/687aa0c5581b
- [net,v4,3/3] vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local`
https://git.kernel.org/netdev/net/c/1e7d9df379a0
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-07-08 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 15:18 [PATCH net v4 0/3] vsock: Fix transport_{h2g,g2h,dgram,local} TOCTOU issues Michal Luczaj
2025-07-03 15:18 ` [PATCH net v4 1/3] vsock: Fix transport_{g2h,h2g} TOCTOU Michal Luczaj
2025-07-03 15:18 ` [PATCH net v4 2/3] vsock: Fix transport_* TOCTOU Michal Luczaj
2025-07-03 15:18 ` [PATCH net v4 3/3] vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` Michal Luczaj
2025-07-08 16:00 ` 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=175199041100.4117860.14540554652345521469.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=stefanha@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