>>> On 04.12.17 at 12:31, wrote:
> On 12/04/2017 09:02 AM, Jan Beulich wrote:
> On 01.12.17 at 16:31, wrote:
>>> On 30/11/17 14:32, Jan Beulich wrote:
Dropping the lock before returning from grant_map_exists() means handing
possibly stale information back to the caller. Return back
On 12/04/2017 09:02 AM, Jan Beulich wrote:
On 01.12.17 at 16:31, wrote:
>> On 30/11/17 14:32, Jan Beulich wrote:
>>> Dropping the lock before returning from grant_map_exists() means handing
>>> possibly stale information back to the caller. Return back the pointer
>>> to the active entry inst
>>> On 01.12.17 at 16:31, wrote:
> On 30/11/17 14:32, Jan Beulich wrote:
>> Dropping the lock before returning from grant_map_exists() means handing
>> possibly stale information back to the caller. Return back the pointer
>> to the active entry instead, for the caller to release the lock once
>>
On Thu, 30 Nov 2017, Jan Beulich wrote:
> Dropping the lock before returning from grant_map_exists() means handing
> possibly stale information back to the caller. Return back the pointer
> to the active entry instead, for the caller to release the lock once
> done.
>
> Signed-off-by: Jan Beulich
Hi,
On 30/11/17 14:32, Jan Beulich wrote:
> Dropping the lock before returning from grant_map_exists() means handing
> possibly stale information back to the caller. Return back the pointer
> to the active entry instead, for the caller to release the lock once
> done.
I don't know enough about gr
Dropping the lock before returning from grant_map_exists() means handing
possibly stale information back to the caller. Return back the pointer
to the active entry instead, for the caller to release the lock once
done.
Signed-off-by: Jan Beulich
--- a/xen/common/grant_table.c
+++ b/xen/common/gr
