From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: Scott Davis <scottwd@gmail.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Scott Davis <scott.davis@starlab.io>,
Ian Jackson <iwj@xenproject.org>, Wei Liu <wl@xen.org>,
George Dunlap <george.dunlap@citrix.com>,
Nick Rosbrook <rosbrookn@ainfosec.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Juergen Gross <jgross@suse.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
"Daniel P . Smith" <dpsmith@apertussolutions.com>
Subject: Re: [XEN PATCH] tools/xl: Add device_model_stubdomain_init_seclabel option to xl.cfg
Date: Tue, 27 Jul 2021 14:19:11 +0200 [thread overview]
Message-ID: <YP/5wL2p/CGR5g7D@mail-itl> (raw)
In-Reply-To: <CAKf6xpvZZCdEbPoetXabX15yL_oMnya0813-nrm6+WagL3Wx3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On Mon, Jul 26, 2021 at 09:07:03AM -0400, Jason Andryuk wrote:
> Sort of relatedly, is stubdom unpaused before the guest gets
> relabeled? Quickly looking, I think stubdom is unpaused. I would
> think you want them both relabeled before either is unpaused. If the
> stubdom starts with the exec_label, but it sees the guest with the
> init_label, it may get an unexpected denial? On the other hand,
> delayed unpausing of stubdom would slow down booting.
Some parts of the stubdomain setup are done after it's unpaused (but
before the guest is unpaused). Especially, PCI devices are hot-plugged
only when QEMU is already running (not sure why).
> With the stubdom getting unpaused before relabel, do you have to give
> the stubdom some extra flask policy permissions to handle that case?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-27 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 4:47 [XEN PATCH] tools/xl: Add device_model_stubdomain_init_seclabel option to xl.cfg Scott Davis
2021-07-26 13:07 ` Jason Andryuk
2021-07-27 12:19 ` Marek Marczykowski-Górecki [this message]
2021-07-27 13:32 ` Ian Jackson
2021-07-27 13:50 ` Jason Andryuk
2021-07-28 12:19 ` Anthony PERARD
2021-07-28 22:11 ` Scott Davis
2021-07-27 11:45 ` Andrew Cooper
2021-07-27 13:30 ` 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=YP/5wL2p/CGR5g7D@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=anthony.perard@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=dpsmith@apertussolutions.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jandryuk@gmail.com \
--cc=jgross@suse.com \
--cc=rosbrookn@ainfosec.com \
--cc=scott.davis@starlab.io \
--cc=scottwd@gmail.com \
--cc=wl@xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.