[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173117463650.2982634.15058723153321836911.git-patchwork-notify@kernel.org>
Date: Sat, 09 Nov 2024 17:50:36 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Hyunwoo Kim <v4bel@...ori.io>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, sgarzare@...hat.com, mst@...hat.com,
jasowang@...hat.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
linux-hyperv@...r.kernel.org, virtualization@...ts.linux.dev,
netdev@...r.kernel.org, gregkh@...uxfoundation.org, imv4bel@...il.com
Subject: Re: [PATCH v2] hv_sock: Initializing vsk->trans to NULL to prevent a
dangling pointer
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 6 Nov 2024 04:36:04 -0500 you wrote:
> When hvs is released, there is a possibility that vsk->trans may not
> be initialized to NULL, which could lead to a dangling pointer.
> This issue is resolved by initializing vsk->trans to NULL.
>
> Fixes: ae0078fcf0a5 ("hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)")
> Cc: stable@...r.kernel.org
> Signed-off-by: Hyunwoo Kim <v4bel@...ori.io>
>
> [...]
Here is the summary with links:
- [v2] hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer
https://git.kernel.org/netdev/net-next/c/e629295bd60a
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