From: Sergiy Kibrik <Sergiy_Kibrik@epam.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>
Subject: Re: [PATCH v1 2/2] common: dom0less-bindings: introduce XSM labels
Date: Fri, 4 Sep 2026 10:01:58 +0000 [thread overview]
Message-ID: <4839ad1a-f75d-4fc2-90fc-6feea58e7ef6@epam.com> (raw)
In-Reply-To: <d98bff6b-c32c-4c52-bbc9-cf88e4be6c3f@citrix.com>
On 8/31/26 13:19, Andrew Cooper wrote:
> To this specifically, I'm not sure security_context_to_sid() handing out
> SECINITSID_XEN if you happen to call it too early is the wisest
> behaviour. It's current call-chain has an earlier check which I think
> excludes this from occurring.
It's only call-chain is in FLASK_CONTEXT_TO_SID xsm_op handling, and it
does return SECINITSID_XEN to toolstack if called before policy is
loaded (I've tried booting with flask=late).
But what's the point of falling back to SECINITSID_XEN anyway?
-Sergiy
next prev parent reply other threads:[~2026-09-04 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 9:38 [PATCH v1 0/2] XSM labels support in dom0less Sergiy Kibrik
2026-08-27 9:38 ` [PATCH v1 2/2] common: dom0less-bindings: introduce XSM labels Sergiy Kibrik
2026-08-27 18:09 ` Daniel P. Smith
2026-08-31 10:19 ` Andrew Cooper
2026-09-04 10:01 ` Sergiy Kibrik [this message]
2026-08-27 9:38 ` [PATCH v1 1/2] flask: add const qualifier to security_context_to_sid() Sergiy Kibrik
2026-08-27 18:08 ` Daniel P. Smith
2026-08-28 6:40 ` Jan Beulich
2026-08-31 10:01 ` Sergiy Kibrik
2026-09-01 6:34 ` Jan Beulich
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=4839ad1a-f75d-4fc2-90fc-6feea58e7ef6@epam.com \
--to=sergiy_kibrik@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=dpsmith@apertussolutions.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.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 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.