On Thu, Nov 07, 2024 at 11:29:42AM -0800, Jakub Kicinski wrote:
> 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: sta...@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?
I think it's just an accent, in certain languages/cultures expressing
uncertainty is considered polite. Should be "can".
--
MST
