Re: [PATCH 08/11] xen/cpupool: prevent a domain from moving itself

["Jürgen Groß" <juergen.gross@ts.fujitsu.com>]

Am 12.04.2013 23:04, schrieb Daniel De Graaf:
> In the XEN_SYSCTL_CPUPOOL_OP_MOVEDOMAIN operation, the existing check
> for domid == 0 should be checking that a domain does not attempt to
> modify its own cpupool; fix this by using rcu_lock_remote_domain_by_id.
>
> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
> Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>
> Cc: Jan Beulich <JBeulich@suse.com>

Sorry for late answer, but I'm on vacation and reading mails not very 
often...

Acked-by: Juergen Gross <juergen.gross@ts.fujitsu.com>

> ---
>   xen/common/cpupool.c | 8 ++------
>   1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/xen/common/cpupool.c b/xen/common/cpupool.c
> index 10b10f8..c901f7e 100644
> --- a/xen/common/cpupool.c
> +++ b/xen/common/cpupool.c
> @@ -546,12 +546,8 @@ int cpupool_do_sysctl(struct xen_sysctl_cpupool_op *op)
>       {
>           struct domain *d;
>
> -        ret = -EINVAL;
> -        if ( op->domid == 0 )
> -            break;
> -        ret = -ESRCH;
> -        d = rcu_lock_domain_by_id(op->domid);
> -        if ( d == NULL )
> +        ret = rcu_lock_remote_domain_by_id(op->domid, &d);
> +        if ( ret )
>               break;
>           if ( d->cpupool == NULL )
>           {
>