From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Paul Durrant <paul.durrant@citrix.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH v3 3/3] xen/privcmd: add IOCTL_PRIVCMD_RESTRICT
Date: Mon, 13 Feb 2017 14:20:27 -0500 [thread overview]
Message-ID: <98d4ae78-98f0-c3fd-e8c8-cdb18a7936e1@oracle.com> (raw)
In-Reply-To: <1487005404-3183-4-git-send-email-paul.durrant@citrix.com>
On 02/13/2017 12:03 PM, Paul Durrant wrote:
> The purpose if this ioctl is to allow a user of privcmd to restrict its
> operation such that it will no longer service arbitrary hypercalls via
> IOCTL_PRIVCMD_HYPERCALL, and will check for a matching domid when
> servicing IOCTL_PRIVCMD_DM_OP.
and IOCTL_PRIVCMD_MMAP*.
> The aim of this is to limit the attack
> surface for a compromised device model.
-boris
next prev parent reply other threads:[~2017-02-13 19:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 17:03 [PATCH v3 0/3] xen/privcmd: support for dm_op and restriction Paul Durrant
2017-02-13 17:03 ` [PATCH v3 1/3] xen/privcmd: return -ENOTTY for unimplemented IOCTLs Paul Durrant
2017-02-13 18:52 ` Boris Ostrovsky
2017-02-13 17:03 ` [PATCH v3 2/3] xen/privcmd: Add IOCTL_PRIVCMD_DM_OP Paul Durrant
2017-02-13 19:11 ` Boris Ostrovsky
2017-02-14 9:20 ` Paul Durrant
2017-02-14 14:11 ` Boris Ostrovsky
2017-02-14 17:25 ` Boris Ostrovsky
2017-02-14 18:38 ` Stefano Stabellini
2017-02-15 9:14 ` Paul Durrant
2017-02-15 14:47 ` Boris Ostrovsky
2017-02-13 17:03 ` [PATCH v3 3/3] xen/privcmd: add IOCTL_PRIVCMD_RESTRICT Paul Durrant
2017-02-13 19:20 ` Boris Ostrovsky [this message]
2017-02-15 14:49 ` Boris Ostrovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98d4ae78-98f0-c3fd-e8c8-cdb18a7936e1@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome