From: Ian Jackson <ian.jackson@eu.citrix.com>
To: qemu-devel@nongnu.org
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: [Qemu-devel] [PATCH v5 0/8] xen: xen-domid-restrict improvements
Date: Thu, 19 Oct 2017 17:51:48 +0100 [thread overview]
Message-ID: <1508431916-9412-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
I have been working on trying to get qemu, when running as a Xen
device model, to _actually_ not have power equivalent to root.
I think I have achieved this, with some limitations (which are
discussed in my series against xen.git.
However, there are changes to qemu needed. In particular
* The -xen-domid-restrict option does not work properly right now.
It only restricts a small subset of the descriptors qemu has open.
I am introducing a new library call in the Xen libraries for this,
xentoolcore_restrict_all.
* We need to call a different function on domain shutdown.
* The restriction operation needs to be done at a slightly different
time, necessitating a new hook.
* Additionally, we want to be able to set aside a uid range for these
qemus to run in, and that involves being able to tell qemu to drop
privilege by numeric uid and gid.
Thanks to Anthony Perard, Ross Lagerwall, Peter Maydell, Markus
Armbruster and Daniel P. Berrange for assistance, review and testing.
m 1/8 xen: link against xentoolcore
r 2/8 xen: restrict: use xentoolcore_restrict_all
rm 3/8 xen: defer call to xen_restrict until just before
r 4/8 xen: destroy_hvm_domain: Move reason into a variable
a 5/8 xen: move xc_interface compatibility fallback further up
r 6/8 xen: destroy_hvm_domain: Try xendevicemodel_shutdown
* 7/8 os-posix: Provide new -runas <uid>.<gid> facility
8/8 configure: do_compiler: Dump some extra info under bash
m = commit message (only) changed in v5 of the series
* = patch changed in v5 of the series
r = reviewed
a = acked
Thanks,
Ian.
next reply other threads:[~2017-10-19 16:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 16:51 Ian Jackson [this message]
2017-10-19 16:51 ` [Qemu-devel] [PATCH 1/8] xen: link against xentoolcore Ian Jackson
2017-10-19 16:51 ` [Qemu-devel] [PATCH 2/8] xen: restrict: use xentoolcore_restrict_all Ian Jackson
2017-10-19 16:51 ` [Qemu-devel] [PATCH 3/8] xen: defer call to xen_restrict until just before os_setup_post Ian Jackson
2017-10-19 16:51 ` [Qemu-devel] [PATCH 4/8] xen: destroy_hvm_domain: Move reason into a variable Ian Jackson
2017-10-19 16:51 ` [Qemu-devel] [PATCH 5/8] xen: move xc_interface compatibility fallback further up the file Ian Jackson
2017-10-19 16:51 ` [Qemu-devel] [PATCH 6/8] xen: destroy_hvm_domain: Try xendevicemodel_shutdown Ian Jackson
2017-10-19 16:51 ` [Qemu-devel] [PATCH 7/8] os-posix: Provide new -runas <uid>.<gid> facility Ian Jackson
2017-10-19 16:51 ` [Qemu-devel] [PATCH 8/8] configure: do_compiler: Dump some extra info under bash Ian Jackson
2017-10-19 18:56 ` [Qemu-devel] [PATCH v5 0/8] xen: xen-domid-restrict improvements no-reply
2017-10-20 10:32 ` Ian Jackson
2017-10-20 13:30 ` Anthony PERARD
2017-10-20 13:37 ` Ian Jackson
2017-10-20 13:38 ` [Qemu-devel] [PATCH v5.1 1/8] xen: link against xentoolcore Ian Jackson
2017-10-20 13:38 ` [Qemu-devel] [PATCH v5.1 2/8] xen: restrict: use xentoolcore_restrict_all Ian Jackson
2017-10-26 21:35 ` Stefano Stabellini
2017-10-27 10:30 ` Ian Jackson
2017-10-27 17:20 ` Stefano Stabellini
2017-10-20 13:38 ` [Qemu-devel] [PATCH v5.1 3/8] xen: defer call to xen_restrict until just before os_setup_post Ian Jackson
2017-10-26 21:37 ` Stefano Stabellini
2017-10-20 13:38 ` [Qemu-devel] [PATCH v5.1 4/8] xen: destroy_hvm_domain: Move reason into a variable Ian Jackson
2017-10-26 21:38 ` Stefano Stabellini
2017-10-20 13:38 ` [Qemu-devel] [PATCH v5.1 5/8] xen: move xc_interface compatibility fallback further up the file Ian Jackson
2017-10-26 22:55 ` Stefano Stabellini
2017-10-20 13:38 ` [Qemu-devel] [PATCH v5.1 6/8] xen: destroy_hvm_domain: Try xendevicemodel_shutdown Ian Jackson
2017-10-26 22:26 ` Stefano Stabellini
2017-10-27 10:16 ` Ian Jackson
2017-10-20 13:38 ` [Qemu-devel] [PATCH v5.1 7/8] os-posix: Provide new -runas <uid>:<gid> facility Ian Jackson
2017-10-24 17:29 ` Anthony PERARD
2017-10-24 18:19 ` Ian Jackson
2017-10-26 22:29 ` Stefano Stabellini
2017-10-27 10:33 ` Ian Jackson
2017-10-20 13:38 ` [Qemu-devel] [PATCH v5.1 8/8] configure: do_compiler: Dump some extra info under bash Ian Jackson
[not found] ` <1508528463.474221335@apps.rackspace.com>
2017-10-23 11:17 ` [Qemu-devel] [PATCH v5.1 8/8] configure: do_compiler: Dump some extra info under bash [and 1 more messages] Ian Jackson
2017-10-26 22:27 ` [Qemu-devel] [PATCH v5.1 8/8] configure: do_compiler: Dump some extra info under bash Stefano Stabellini
2017-10-27 10:40 ` Ian Jackson
2017-10-26 22:41 ` [Qemu-devel] [PATCH v5.1 1/8] xen: link against xentoolcore Stefano Stabellini
2017-10-27 10:12 ` Ian Jackson
2018-01-24 11:03 ` [Qemu-devel] [PATCH v5 0/8] xen: xen-domid-restrict improvements Ross Lagerwall
2018-01-24 11:31 ` Ian Jackson
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=1508431916-9412-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=jgross@suse.com \
--cc=qemu-devel@nongnu.org \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).