qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: qemu-devel@nongnu.org, Ross Lagerwall <ross.lagerwall@citrix.com>,
	Juergen Gross <jgross@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 05/16] xen: defer call to xen_restrict until just before os_setup_post
Date: Mon, 23 Apr 2018 15:28:22 +0100	[thread overview]
Message-ID: <20180423142822.GA1980@perard> (raw)
In-Reply-To: <1524156319-11465-6-git-send-email-ian.jackson@eu.citrix.com>

On Thu, Apr 19, 2018 at 05:45:08PM +0100, Ian Jackson wrote:
> We need to restrict *all* the control fds that qemu opens.  Looking in
> /proc/PID/fd shows there are many; their allocation seems scattered
> throughout Xen support code in qemu.
> 
> We must postpone the restrict call until roughly the same time as qemu
> changes its uid, chroots (if applicable), and so on.
> 
> There doesn't seem to be an appropriate hook already.  The RunState
> change hook fires at different times depending on exactly what mode
> qemu is operating in.
> 
> And it appears that no-one but the Xen code wants a hook at this phase
> of execution.  So, introduce a bare call to a new function
> xen_setup_post, just before os_setup_post.  Also provide the
> appropriate stub for when Xen compilation is disabled.
> 
> We do the restriction before rather than after os_setup_post, because
> xen_restrict may need to open /dev/null, and os_setup_post might have
> called chroot.
> 
> Currently this does not work with migration, because when running as
> the Xen device model qemu needs to signal to the toolstack that it is
> ready.  It currently does this using xenstore, and for incoming
> migration (but not for ordinary startup) that happens after
> os_setup_post.
> 
> It is correct that this happens late: we want the incoming migration
> stream to be processed by a restricted qemu.  The fix for this will be
> to do the startup notification a different way, without using
> xenstore.  (QMP is probably a reasonable choice.)
> 
> So for now this restriction feature cannot be used in conjunction with
> migration.  (Note that this is not a regression in this patch, because
> previously the -xen-restrict-domid call was, in fact, simply
> ineffective!)  We will revisit this in the Xen 4.11 release cycle.
> 
> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>

Acked-by: Anthony PERARD <anthony.perard@citrix.com>

-- 
Anthony PERARD

  reply	other threads:[~2018-04-23 14:28 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 16:45 [Qemu-devel] [PATCH v7 00/16] xen: xen-domid-restrict improvements Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 01/16] checkpatch: Add xendevicemodel_handle to the list of types Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 02/16] AccelClass: Introduce accel_setup_post Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 03/16] xen: link against xentoolcore Ian Jackson
2018-04-23 15:05   ` Anthony PERARD
2018-04-24 14:28     ` Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 04/16] xen: restrict: use xentoolcore_restrict_all Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 05/16] xen: defer call to xen_restrict until just before os_setup_post Ian Jackson
2018-04-23 14:28   ` Anthony PERARD [this message]
2018-04-23 15:58   ` Anthony PERARD
2018-04-24 15:08     ` Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 06/16] xen: destroy_hvm_domain: Move reason into a variable Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 07/16] xen: move xc_interface compatibility fallback further up the file Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 08/16] xen: destroy_hvm_domain: Try xendevicemodel_shutdown Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 09/16] os-posix: cleanup: Replace fprintfs with error_report in change_process_uid Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 10/16] os-posix: Provide new -runas <uid>:<gid> facility Ian Jackson
2018-04-20 12:56   ` Markus Armbruster
2018-04-19 16:45 ` [Qemu-devel] [PATCH 11/16] xen: Use newly added dmops for mapping VGA memory Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 12/16] xen: Remove now-obsolete xen_xc_domain_add_to_physmap Ian Jackson
2018-04-23 15:38   ` Anthony PERARD
2018-04-19 16:45 ` [Qemu-devel] [PATCH 13/16] xen: Expect xenstore write to fail when restricted Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 14/16] os-posix: cleanup: Replace fprintf with error_report in remaining call sites Ian Jackson
2018-04-19 20:25   ` Philippe Mathieu-Daudé
2018-04-20 10:19     ` Ian Jackson
2018-04-19 16:45 ` [Qemu-devel] [PATCH 15/16] os-posix: cleanup: Replace perror with error_report Ian Jackson
2018-04-19 20:31   ` Philippe Mathieu-Daudé
2018-04-24 14:53     ` Ian Jackson
2018-04-24 15:18       ` Daniel P. Berrangé
2018-04-24 15:40         ` Eric Blake
2018-04-24 15:43           ` Eric Blake
2018-04-24 15:54             ` Daniel P. Berrangé
2018-04-24 16:20     ` Markus Armbruster
2018-04-19 16:45 ` [Qemu-devel] [PATCH 16/16] configure: do_compiler: Dump some extra info under bash Ian Jackson
2018-04-23 16:21   ` Anthony PERARD
2018-04-23 16:38     ` Daniel P. Berrangé
2018-04-23 17:12       ` Ian Jackson
2018-04-23 16:38     ` Ian Jackson
2018-04-23 20:28       ` Eric Blake
2018-04-24 15:05         ` Ian Jackson
2018-04-19 17:03 ` [Qemu-devel] [PATCH v7 00/16] xen: xen-domid-restrict improvements no-reply
  -- strict thread matches above, loose matches on Subject: below --
2018-04-24 17:58 [Qemu-devel] [PATCH v8 " Ian Jackson
2018-04-24 17:58 ` [Qemu-devel] [PATCH 05/16] xen: defer call to xen_restrict until just before os_setup_post 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=20180423142822.GA1980@perard \
    --to=anthony.perard@citrix.com \
    --cc=ehabkost@redhat.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jgross@suse.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ross.lagerwall@citrix.com \
    --cc=rth@twiddle.net \
    --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).