From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
HarshaVardhana S A <harshavardhana.sa@broadcom.com>,
Bryan Tan <bryan-bt.tan@broadcom.com>,
Vishnu Dasa <vishnu.dasa@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
virtualization@lists.linux.dev, stable <stable@kernel.org>
Subject: Re: [PATCH net] vsock/vmci: Clear the vmci transport packet properly when initializing it
Date: Tue, 1 Jul 2025 14:56:14 +0200 [thread overview]
Message-ID: <2025070144-brussels-revisit-9aa3@gregkh> (raw)
In-Reply-To: <37t6cnaqt2g7dyl6lauf7tccm5yzpv3dvxbngv7f7omiah35rr@nl35itdnhuda>
On Tue, Jul 01, 2025 at 02:42:10PM +0200, Stefano Garzarella wrote:
> On Tue, Jul 01, 2025 at 02:22:54PM +0200, Greg Kroah-Hartman wrote:
> > From: HarshaVardhana S A <harshavardhana.sa@broadcom.com>
> >
> > In vmci_transport_packet_init memset the vmci_transport_packet before
> > populating the fields to avoid any uninitialised data being left in the
> > structure.
>
> Usually I would suggest inserting a Fixes tag, but if you didn't put it,
> there's probably a reason :-)
>
> If we are going to add it, I think it should be:
>
> Fixes: d021c344051a ("VSOCK: Introduce VM Sockets")
Yeah, I didn't think it was needed as this is obviously a "ever since
this file has been there" type of thing, so it will be backported
everywhere once it hits Linus's tree.
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-01 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 12:22 [PATCH net] vsock/vmci: Clear the vmci transport packet properly when initializing it Greg Kroah-Hartman
2025-07-01 12:42 ` Stefano Garzarella
2025-07-01 12:56 ` Greg Kroah-Hartman [this message]
2025-07-03 10:50 ` Stefano Garzarella
2025-07-03 10:51 ` Stefano Garzarella
2025-07-03 11:00 ` 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=2025070144-brussels-revisit-9aa3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bryan-bt.tan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harshavardhana.sa@broadcom.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stable@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=vishnu.dasa@broadcom.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