[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <589C8E1D0200007800138448@prv-mh.provo.novell.com>
Date: Thu, 09 Feb 2017 07:43:25 -0700
From: "Jan Beulich" <JBeulich@...e.com>
To: "Paul Durrant" <paul.durrant@...rix.com>
Cc: <xen-devel@...ts.xenproject.org>,
"Boris Ostrovsky" <boris.ostrovsky@...cle.com>,
"Juergen Gross" <JGross@...e.com>, <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH 3/3] xen/privcmd: add
IOCTL_PRIVCMD_RESTRICT
>>> On 09.02.17 at 15:17, <paul.durrant@...rix.com> wrote:
> @@ -666,6 +680,20 @@ static long privcmd_ioctl_dm_op(void __user *udata)
> return rc;
> }
>
> +static long privcmd_ioctl_restrict(struct file *file, void __user *udata)
> +{
> + struct privcmd_data *data = file->private_data;
> + domid_t dom;
> +
> + if (copy_from_user(&dom, udata, sizeof(dom)))
> + return -EFAULT;
> +
> + /* Set restriction to the specified domain */
> + data->domid = dom;
> +
> + return 0;
> +}
Is it really intended for the caller to be able to undo this, by passing
in DOMID_INVALID?
Jan
Powered by blists - more mailing lists