RE: [PATCH v7 1/3] Drivers: hv: vmbus: Add vmbus_requestor data structure for VMBus hardening

2020-09-15 Thread Michael Kelley
From: Andrea Parri (Microsoft) Sent: Monday, September 7, 2020 9:19 AM > > From: Andres Beltran > > 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-

Re: [PATCH v7 1/3] Drivers: hv: vmbus: Add vmbus_requestor data structure for VMBus hardening

2020-09-15 Thread Andrea Parri
On Mon, Sep 14, 2020 at 05:29:11PM +, Michael Kelley wrote: > From: Andrea Parri Sent: Tuesday, September 8, 2020 > 12:54 AM > > > > > > @@ -300,6 +303,22 @@ int hv_ringbuffer_write(struct vmbus_channel > > > > *channel, > > > > > > > >

RE: [PATCH v7 1/3] Drivers: hv: vmbus: Add vmbus_requestor data structure for VMBus hardening

2020-09-14 Thread Michael Kelley
From: Andrea Parri Sent: Tuesday, September 8, 2020 12:54 AM > > > > @@ -300,6 +303,22 @@ int hv_ringbuffer_write(struct vmbus_channel > > > *channel, > > >kv_list[i].iov_len); > > > } > > > > > > + /* > > > + * Allocate the request ID after th

Re: [PATCH v7 1/3] Drivers: hv: vmbus: Add vmbus_requestor data structure for VMBus hardening

2020-09-08 Thread Andrea Parri
> > @@ -300,6 +303,22 @@ int hv_ringbuffer_write(struct vmbus_channel *channel, > > kv_list[i].iov_len); > > } > > > > + /* > > +* Allocate the request ID after the data has been copied into the > > +* ring buffer. Once this request I

RE: [PATCH v7 1/3] Drivers: hv: vmbus: Add vmbus_requestor data structure for VMBus hardening

2020-09-07 Thread Michael Kelley
From: Andrea Parri (Microsoft) Sent: Monday, September 7, 2020 9:19 AM > > From: Andres Beltran > > 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