From: Guido Trentalancia <guido-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] do not umount selinuxfs and sysfs
Date: Mon, 02 Jan 2017 23:09:02 +0100 [thread overview]
Message-ID: <1483394942.7011.2.camel@trentalancia.net> (raw)
In-Reply-To: <1483394668.7011.1.camel-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
When the selinux module is enabled, after loading the SELinux
policy, do not umount selinuxfs and sysfs.
This causes the failure of subsequent calls to the function
is_selinux_enabled() in libselinux which in turn causes a
boot failure on systems using sysvinit because the init daemon
tries load the SELinux policy again.
Signed-off-by: Guido Trentalancia <guido-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
---
modules.d/98selinux/selinux-loadpolicy.sh | 2 --
1 file changed, 2 deletions(-)
--- dracut-044-orig/modules.d/98selinux/selinux-loadpolicy.sh 2017-01-02 21:49:03.760547083 +0100
+++ dracut-044/modules.d/98selinux/selinux-loadpolicy.sh 2017-01-02 22:52:36.485433239 +0100
@@ -34,8 +34,6 @@ rd_load_policy()
ret=$?
info $out
fi
- umount $NEWROOT/sys/fs/selinux
- umount $NEWROOT/sys
if [ "$SELINUX" = "disabled" ]; then
return 0;
next prev parent reply other threads:[~2017-01-02 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 1:15 [PATCH 1/2] load the selinux policy after switching to the new root Guido Trentalancia
[not found] ` <1483319729.2481.2.camel-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
2017-01-02 1:26 ` [PATCH 2/2] do not umount selinuxfs and sysfs Guido Trentalancia
[not found] ` <1483320391.2481.4.camel-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
2017-01-02 22:04 ` Guido Trentalancia
[not found] ` <1483394668.7011.1.camel-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
2017-01-02 22:09 ` Guido Trentalancia [this message]
2017-01-02 21:31 ` [PATCH 1/2] load the selinux policy after switching to the new root Guido Trentalancia
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=1483394942.7011.2.camel@trentalancia.net \
--to=guido-d1bseh+szqhuxeb9wqlrnw@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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