[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <MW2PR2101MB1052E024460AE69A546183B2D76F0@MW2PR2101MB1052.namprd21.prod.outlook.com>
Date: Tue, 30 Jun 2020 18:13:31 +0000
From: Michael Kelley <mikelley@...rosoft.com>
To: Stephen Hemminger <stephen@...workplumber.org>,
Andres Beltran <lkmlabelt@...il.com>
CC: Andres Beltran <t-mabelt@...rosoft.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"parri.andrea@...il.com" <parri.andrea@...il.com>,
Saruhan Karademir <skarade@...rosoft.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"James E . J . Bottomley" <jejb@...ux.ibm.com>,
"Martin K . Petersen" <martin.petersen@...cle.com>,
"David S . Miller" <davem@...emloft.net>
Subject: RE: [PATCH v3 0/3] Drivers: hv: vmbus: vmbus_requestor data structure
for VMBus hardening
From: Stephen Hemminger <stephen@...workplumber.org> Sent: Tuesday, June 30, 2020 10:16 AM
>
> On Tue, 30 Jun 2020 11:31:57 -0400
> Andres Beltran <lkmlabelt@...il.com> wrote:
>
> > Currently, VMbus drivers use pointers into guest memory as request IDs
> > for interactions with Hyper-V. To be more robust in the face of errors
> > or malicious behavior from a compromised Hyper-V, avoid exposing
> > guest memory addresses to Hyper-V. Also avoid Hyper-V giving back a
> > bad request ID that is then treated as the address of a guest data
> > structure with no validation. Instead, encapsulate these memory
> > addresses and provide small integers as request IDs.
> >
> > The first patch creates the definitions for the data structure, provides
> > helper methods to generate new IDs and retrieve data, and
> > allocates/frees the memory needed for vmbus_requestor.
> >
> > The second and third patches make use of vmbus_requestor to send request
> > IDs to Hyper-V in storvsc and netvsc respectively.
> >
> > Thanks.
> > Andres Beltran
> >
> > Tested-by: Andrea Parri <parri.andrea@...il.com>
> >
> > Cc: linux-scsi@...r.kernel.org
> > Cc: netdev@...r.kernel.org
> > Cc: James E.J. Bottomley <jejb@...ux.ibm.com>
> > Cc: Martin K. Petersen <martin.petersen@...cle.com>
> > Cc: David S. Miller <davem@...emloft.net>
> >
> > Andres Beltran (3):
> > Drivers: hv: vmbus: Add vmbus_requestor data structure for VMBus
> > hardening
> > scsi: storvsc: Use vmbus_requestor to generate transaction IDs for
> > VMBus hardening
> > hv_netvsc: Use vmbus_requestor to generate transaction IDs for VMBus
> > hardening
> >
> > drivers/hv/channel.c | 154 ++++++++++++++++++++++++++++++
> > drivers/net/hyperv/hyperv_net.h | 13 +++
> > drivers/net/hyperv/netvsc.c | 79 ++++++++++++---
> > drivers/net/hyperv/rndis_filter.c | 1 +
> > drivers/scsi/storvsc_drv.c | 85 ++++++++++++++---
> > include/linux/hyperv.h | 22 +++++
> > 6 files changed, 329 insertions(+), 25 deletions(-)
> >
>
> How does this interact with use of the vmbus in usermode by DPDK through
> hv_uio_generic?
> Will it still work?
This new mechanism for generating requestIDs to pass to Hyper-V is
available for VMbus drivers to use, but drivers that have not been updated
to use it are unaffected. So hv_uio_generic will work as it always has.
Michael
Powered by blists - more mailing lists