Re: [Xen-devel] [PATCH 3/3] xen: Document XEN_SYSCTL_CPUPOOL_OP_RMCPU anomalous EBUSY result

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Dario Faggioli writes ("Re: [Xen-devel] [PATCH 3/3] xen: Document 
XEN_SYSCTL_CPUPOOL_OP_RMCPU anomalous EBUSY result"):
> On Thu, 2016-04-14 at 18:56 +0100, Ian Jackson wrote:
> > is very unfortunate.  How is a toolstack to know what to do ?
> > 
> Yeah, I agree, but again, I think in this case it's possible for
> toolstack to tell.

Thanks to both you and Juergen for the explanations.  I'm glad to see
that things weren't as bad as I feared - I admit that I didn't spend
the time to completely follow what all the relevant bits of code did.

Would either of you care to provide a version of my documentation patch
which answers the questions that my text answers ?  Or shall we commit
my version and you can edit it in-tree :-).

>         ret = -EPERM;
>         if ( !is_hardware_domain(current->domain) )
>             break;
> 
> which I think satisfies Ian's (legitimate) concern?

That addresses the security concern, yes.  (Is a driver domain a
`hardware domain' in this sense?)

All I need now is a recipe for the tools to tell what has happened and
then I can make xl or libxl at least print comprehensible and correct
error messages...

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel