From: Anshul Makkar <anshul.makkar@citrix.com>
To: xen-devel@lists.xen.org
Cc: dgdegra@tycho.nsa.gov, ian.jackson@eu.citrix.com,
Anshul Makkar <anshul.makkar@citrix.com>
Subject: [PATCH] XSM-Policy: allow source domain access to setpodtarget for ballooning.
Date: Wed, 13 Jul 2016 13:59:37 +0100 [thread overview]
Message-ID: <1468414777-27129-1-git-send-email-anshul.makkar@citrix.com> (raw)
Access to setpodtarget is required by dom0 to set the balloon targets for
domU. The patch gives source domain (dom0) access to set this target for
domU and resolve the following permission denied error message during
ballooning :
avc: denied { setpodtarget } for domid=0 target=9
scontext=system_u:system_r:dom0_t
tcontext=system_u:system_r:domU_t tclass=domain
Signed-off-by: Anshul Makkar <anshul.makkar@citrix.com>
---
---
tools/flask/policy/modules/xen.if | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/flask/policy/modules/xen.if b/tools/flask/policy/modules/xen.if
index 8c43c28..8ae3c2e 100644
--- a/tools/flask/policy/modules/xen.if
+++ b/tools/flask/policy/modules/xen.if
@@ -83,7 +83,8 @@ define(`create_domain_build_label', `
define(`manage_domain', `
allow $1 $2:domain { getdomaininfo getvcpuinfo getaffinity
getaddrsize pause unpause trigger shutdown destroy
- setaffinity setdomainmaxmem getscheduler resume };
+ setaffinity setdomainmaxmem getscheduler resume
+ setpodtarget };
allow $1 $2:domain2 set_vnumainfo;
')
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-07-13 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 12:59 Anshul Makkar [this message]
2016-07-13 17:28 ` [PATCH] XSM-Policy: allow source domain access to setpodtarget for ballooning Daniel De Graaf
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=1468414777-27129-1-git-send-email-anshul.makkar@citrix.com \
--to=anshul.makkar@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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).