All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: kvm@vger.kernel.org, Cristian Marussi <cristian.marussi@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH kvmtool] virtio/pci: explicit zero unknown devices features
Date: Thu, 14 Aug 2025 17:07:35 +0100	[thread overview]
Message-ID: <aJ4Jx784CjBgY1pz@pluto> (raw)
In-Reply-To: <ed62443b8fd3fef87bd313a54f821cf363f647a5.1755185758.git.pabeni@redhat.com>

On Thu, Aug 14, 2025 at 05:37:02PM +0200, Paolo Abeni wrote:
> The linux kernel implementation for the virtio_net driver recently
> gained support for virtio features above the 64th bit.
> 

Hi,

> It relies on the hypervisor to clear the features data for unknown /
> unsupported features range.
> 
> The current pci-modern implementation, in such scenario, leaves the
> data memory untouched, which causes the guest kernel assuming "random"
> features are supported (and possibly leaks host memory contents).
> 
> Explicitly clear the features data for unsupported range.
> 

This patch definitely solves for me the virtio networking issue reported at:

https://lore.kernel.org/virtualization/c25f924f-a66b-47cc-819d-5ed241a4bac6@redhat.com/T/#t

Tested on an arm64 Host (v6.14.8) with a v6.17-rc1 Guest.

Thanks !

Tested-by: Cristian Marussi <cristian.marussi@arm.com>

Thanks,
Cristian

  reply	other threads:[~2025-08-14 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 15:37 [PATCH kvmtool] virtio/pci: explicit zero unknown devices features Paolo Abeni
2025-08-14 16:07 ` Cristian Marussi [this message]
2025-08-19 11:01 ` Will Deacon

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=aJ4Jx784CjBgY1pz@pluto \
    --to=cristian.marussi@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=will@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.