From db465c684adb917f0751776b362ef7fd8a33b188 Mon Sep 17 00:00:00 2001
Message-Id: <db465c684adb917f0751776b362ef7fd8a33b188.1377873638.git.jdenemar@redhat.com>
From: Dan Walsh <dwalsh@redhat.com>
Date: Tue, 13 Aug 2013 11:37:29 +0100
Subject: [PATCH] Ensure securityfs is mounted readonly in container

For https://bugzilla.redhat.com/show_bug.cgi?id=872642

If securityfs is available on the host, we should ensure to
mount it read-only in the container. This will avoid systemd
trying to mount it during startup causing SELinux AVCs.

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
(cherry picked from commit 6807238d87fd93dee30038bea1e8582a5f0a9fe7)
---
 src/lxc/lxc_container.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/lxc/lxc_container.c b/src/lxc/lxc_container.c
index b910b10..a943b22 100644
--- a/src/lxc/lxc_container.c
+++ b/src/lxc/lxc_container.c
@@ -770,6 +770,8 @@ static int lxcContainerMountBasicFS(void)
         { "/proc/sys", "/proc/sys", NULL, NULL, MS_BIND|MS_REMOUNT|MS_RDONLY },
         { "sysfs", "/sys", "sysfs", NULL, MS_NOSUID|MS_NOEXEC|MS_NODEV },
         { "sysfs", "/sys", "sysfs", NULL, MS_BIND|MS_REMOUNT|MS_RDONLY },
+        { "securityfs", "/sys/kernel/security", "securityfs", NULL, MS_NOSUID|MS_NOEXEC|MS_NODEV },
+        { "securityfs", "/sys/kernel/security", "securityfs", NULL, MS_BIND|MS_REMOUNT|MS_RDONLY },
 #if WITH_SELINUX
         { SELINUX_MOUNT, SELINUX_MOUNT, "selinuxfs", NULL, MS_NOSUID|MS_NOEXEC|MS_NODEV },
         { SELINUX_MOUNT, SELINUX_MOUNT, NULL, NULL, MS_BIND|MS_REMOUNT|MS_RDONLY },
-- 
1.8.3.2