Re: [PATCH v3 2/7] xen/memory: Fix acquire_resource size semantics

2021-01-12 Thread Tamas K Lengyel
On Tue, Jan 12, 2021 at 3:57 PM Andrew Cooper wrote: > > On 12/01/2021 20:15, Julien Grall wrote: > > Hi Andrew, > > > > On Tue, 12 Jan 2021 at 19:49, Andrew Cooper > > wrote: > >> Calling XENMEM_acquire_resource with a NULL frame_list is a request for the > >> size of the resource, but the retu

Re: [PATCH v3 2/7] xen/memory: Fix acquire_resource size semantics

2021-01-12 Thread Andrew Cooper
On 12/01/2021 20:15, Julien Grall wrote: > Hi Andrew, > > On Tue, 12 Jan 2021 at 19:49, Andrew Cooper wrote: >> Calling XENMEM_acquire_resource with a NULL frame_list is a request for the >> size of the resource, but the returned 32 is bogus. >> >> If someone tries to follow it for XENMEM_resource

Re: [PATCH v3 2/7] xen/memory: Fix acquire_resource size semantics

2021-01-12 Thread Julien Grall
Hi Andrew, On Tue, 12 Jan 2021 at 19:49, Andrew Cooper wrote: > > Calling XENMEM_acquire_resource with a NULL frame_list is a request for the > size of the resource, but the returned 32 is bogus. > > If someone tries to follow it for XENMEM_resource_ioreq_server, the acquire > call will fail as I

[PATCH v3 2/7] xen/memory: Fix acquire_resource size semantics

2021-01-12 Thread Andrew Cooper
Calling XENMEM_acquire_resource with a NULL frame_list is a request for the size of the resource, but the returned 32 is bogus. If someone tries to follow it for XENMEM_resource_ioreq_server, the acquire call will fail as IOREQ servers currently top out at 2 frames, and it is only half the size of