From: Jan Beulich <jbeulich@suse.com>
To: "Daniel P. Smith" <dpsmith@apertussolutions.com>
Cc: jandryuk@gmail.com, Wei Liu <wl@xen.org>,
Anthony PERARD <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v11] xsm: refactor flask sid alloc and domain check
Date: Wed, 3 Aug 2022 17:26:37 +0200 [thread overview]
Message-ID: <f9001446-157a-99a6-29cd-dcbbb6d59527@suse.com> (raw)
In-Reply-To: <20220803151741.7826-1-dpsmith@apertussolutions.com>
On 03.08.2022 17:17, Daniel P. Smith wrote:
> Changes in v11:
> - put back dom0_created variable in flask_domain_create() to ensure the
> enforcement that dom0_t is a singleton label
Stale patch or bad rev log?
> @@ -548,22 +556,19 @@ static int cf_check flask_domain_create(struct domain *d, uint32_t ssidref)
> {
> int rc;
> struct domain_security_struct *dsec = d->ssid;
> - static int dom0_created = 0;
The variable is going away here, and it is not re-appearing elsewhere.
Jan
> - if ( is_idle_domain(current->domain) && !dom0_created )
> - {
> - dsec->sid = SECINITSID_DOM0;
> - dom0_created = 1;
> - }
> - else
> - {
> - rc = avc_current_has_perm(ssidref, SECCLASS_DOMAIN,
> - DOMAIN__CREATE, NULL);
> - if ( rc )
> - return rc;
> + /*
> + * If the null label is passed, then use the label from security context
> + * allocation.
> + */
> + if ( ssidref == 0 )
> + ssidref = dsec->sid;
>
> - dsec->sid = ssidref;
> - }
> + rc = avc_current_has_perm(ssidref, SECCLASS_DOMAIN, DOMAIN__CREATE, NULL);
> + if ( rc )
> + return rc;
> +
> + dsec->sid = ssidref;
> dsec->self_sid = dsec->sid;
>
> rc = security_transition_sid(dsec->sid, dsec->sid, SECCLASS_DOMAIN,
next prev parent reply other threads:[~2022-08-03 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 15:17 [PATCH v11] xsm: refactor flask sid alloc and domain check Daniel P. Smith
2022-08-03 15:26 ` Jan Beulich [this message]
2022-08-03 15:52 ` Daniel P. Smith
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=f9001446-157a-99a6-29cd-dcbbb6d59527@suse.com \
--to=jbeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=jandryuk@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.