All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] system/init: move systemd_ interfaces into optional_policy
Date: Mon, 7 Mar 2016 09:56:31 -0500	[thread overview]
Message-ID: <56DD969F.4000701@tresys.com> (raw)
In-Reply-To: <1457340336-4516-1-git-send-email-jason@perfinion.com>

On 3/7/2016 3:45 AM, Jason Zaman wrote:
> When ifdef systemd is enabled, some interfaces from systemd are called
> unconditionally. This makes migrating from non-systemd to systemd
> complicated since init is part of base and systemd is not so loading
> fails. Moving them into optional_policy fixes this.
> ---
>  policy/modules/system/init.te | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/policy/modules/system/init.te b/policy/modules/system/init.te
> index c9e1532..fb7aafc 100644
> --- a/policy/modules/system/init.te
> +++ b/policy/modules/system/init.te
> @@ -280,13 +280,15 @@ ifdef(`init_systemd',`
>  
>  	seutil_read_file_contexts(init_t)
>  
> -	systemd_relabelto_kmod_files(init_t)
> -	systemd_dbus_chat_logind(init_t)
> -
>  	# udevd is a "systemd kobject uevent socket activated daemon"
>  	udev_create_kobject_uevent_sockets(init_t)
>  
>  	optional_policy(`
> +		systemd_relabelto_kmod_files(init_t)
> +		systemd_dbus_chat_logind(init_t)
> +	')
> +
> +	optional_policy(`
>  		dbus_system_bus_client(init_t)
>  		dbus_connect_system_bus(init_t)
>  	')

I don't think I follow.  The lines are already in the init_systemd
block, so it doesn't make sense for them to be optional.  Why wouldn't
systemd be in base, in this situation?

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2016-03-07 14:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07  8:45 [refpolicy] [PATCH] system/init: move systemd_ interfaces into optional_policy Jason Zaman
2016-03-07 14:56 ` Christopher J. PeBenito [this message]
2016-03-07 15:33   ` Jason Zaman
2016-03-08 13:53 ` Christopher J. PeBenito

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=56DD969F.4000701@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=refpolicy@oss.tresys.com \
    /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.