From: Jakub Kicinski <kuba@kernel•org>
To: Hyunwoo Kim <v4bel@theori•io>
Cc: "K. Y. Srinivasan" <kys@microsoft•com>,
Haiyang Zhang <haiyangz@microsoft•com>,
Wei Liu <wei.liu@kernel•org>, Dexuan Cui <decui@microsoft•com>,
Stefano Garzarella <sgarzare@redhat•com>,
mst@redhat•com, jasowang@redhat•com,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>, Simon Horman <horms@kernel•org>,
linux-hyperv@vger•kernel.org, virtualization@lists•linux.dev,
netdev@vger•kernel.org, gregkh@linuxfoundation•org,
imv4bel@gmail•com
Subject: Re: [PATCH v2] hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer
Date: Thu, 7 Nov 2024 11:29:42 -0800 [thread overview]
Message-ID: <20241107112942.0921eb65@kernel.org> (raw)
In-Reply-To: <Zys4hCj61V+mQfX2@v4bel-B760M-AORUS-ELITE-AX>
On Wed, 6 Nov 2024 04:36:04 -0500 Hyunwoo Kim 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@vger•kernel.org
I don't see the v1 on netdev@, nor a link to it in the change log
so I may be missing the context, but the commit message is a bit
sparse.
The stable and Fixes tags indicate this is a fix. But the commit
message reads like currently no such crash is observed, quote:
which could lead to a dangling pointer.
^^^^^
?
Could someone clarify?
next prev parent reply other threads:[~2024-11-07 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 9:36 [PATCH v2] hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer Hyunwoo Kim
2024-11-06 9:41 ` Stefano Garzarella
2024-11-06 9:42 ` Michael S. Tsirkin
2024-11-07 19:29 ` Jakub Kicinski [this message]
2024-11-07 21:41 ` Michael S. Tsirkin
2024-11-07 21:52 ` Jakub Kicinski
2024-11-08 9:06 ` Hyunwoo Kim
2024-11-09 17:50 ` patchwork-bot+netdevbpf
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=20241107112942.0921eb65@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=decui@microsoft$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=haiyangz@microsoft$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=imv4bel@gmail$(echo .)com \
--cc=jasowang@redhat$(echo .)com \
--cc=kys@microsoft$(echo .)com \
--cc=linux-hyperv@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=sgarzare@redhat$(echo .)com \
--cc=v4bel@theori$(echo .)io \
--cc=virtualization@lists$(echo .)linux.dev \
--cc=wei.liu@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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