From: Markus Elfring <Markus.Elfring@web.de>
To: Henry Martin <bsdhenryma@tencent.com>,
virtualization@lists.linux.dev, kvm@vger.kernel.org,
netdev@vger.kernel.org
Cc: tcs_robot@tencent.com, LKML <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
huntazhang@tencent.com, "Jakub Kicinski" <kuba@kernel.org>,
"Jason Wang" <jasowang@redhat.com>,
jitxie@tencent.com, landonsun@tencent.com,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH] VSOCK: fix Information Leak in virtio_transport_shutdown()
Date: Tue, 5 Aug 2025 10:08:11 +0200 [thread overview]
Message-ID: <c90910d8-a4e4-4238-95e7-9a2d052cf52f@web.de> (raw)
In-Reply-To: <20250805051009.1766587-1-tcs_kernel@tencent.com>
> The `struct virtio_vsock_pkt_info` is declared on the stack but only
> partially initialized (only `op`, `flags`, and `vsk` are set)
…
See also once more:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n94
Would a summary phrase like “Prevent information leak in virtio_transport_shutdown()”
be nicer?
Regards,
Markus
prev parent reply other threads:[~2025-08-05 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 5:10 [PATCH v1] VSOCK: fix Information Leak in virtio_transport_shutdown() bsdhenrymartin
2025-08-05 6:55 ` Wang Liang
2025-08-05 7:00 ` Stefano Garzarella
2025-08-05 8:53 ` henry martin
2025-08-05 8:08 ` Markus Elfring [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=c90910d8-a4e4-4238-95e7-9a2d052cf52f@web.de \
--to=markus.elfring@web.de \
--cc=bsdhenryma@tencent.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=huntazhang@tencent.com \
--cc=jasowang@redhat.com \
--cc=jitxie@tencent.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=landonsun@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=tcs_robot@tencent.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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