On Thu, Jan 19, 2017 at 01:56:34PM +, Andrew Cooper wrote:
> On 19/01/17 11:01, Wei Liu wrote:
> > On Wed, Jan 18, 2017 at 07:15:44PM +0100, Juergen Gross wrote:
> > [...]
> >> diff --git a/xen/include/public/io/xs_wire.h
> >> b/xen/include/public/io/xs_wire.h
> >> index 54c1d71..751bd17 10064
On 19/01/17 11:01, Wei Liu wrote:
> On Wed, Jan 18, 2017 at 07:15:44PM +0100, Juergen Gross wrote:
> [...]
>> diff --git a/xen/include/public/io/xs_wire.h
>> b/xen/include/public/io/xs_wire.h
>> index 54c1d71..751bd17 100644
>> --- a/xen/include/public/io/xs_wire.h
>> +++ b/xen/include/public/io/x
On Wed, Jan 18, 2017 at 07:15:44PM +0100, Juergen Gross wrote:
[...]
> diff --git a/xen/include/public/io/xs_wire.h b/xen/include/public/io/xs_wire.h
> index 54c1d71..751bd17 100644
> --- a/xen/include/public/io/xs_wire.h
> +++ b/xen/include/public/io/xs_wire.h
> @@ -48,7 +48,7 @@ enum xsd_sockmsg_
XS_RESTRICT and the xenstore library function xs_restrict() have never
been usable in all configurations and there are no known users.
This functionality was thought to limit access rights of device models
to xenstore in order to avoid affecting other domains in case of a
security breech. Unfortun
