The patch titled
panic on SLIM + selinux
has been removed from the -mm tree. Its filename was
panic-on-slim-selinux.patch
This patch was dropped because it was folded into slim-make-and-config-stuff.patch
------------------------------------------------------
Subject: panic on SLIM + selinux
From: Daniel Walker <dwalker@xxxxxxxxxx>
If you have both SLIM and selinux compiled into your kernel selinux will
panic if it can't register itself. The code below,
if (register_security (&selinux_ops))
panic("SELinux: Unable to register with kernel.\n");
"security/selinux/hooks.c" 5014 lines --95%-- 4811,35 96%
This could be a bug report cause I bet there's a better way to make these
mutually exclusive.
Signed-off-by: Daniel Walker <dwalker@xxxxxxxxxx>
Cc: Mimi Zohar <zohar@xxxxxxxxxx>
Cc: Kylene Hall <kjhall@xxxxxxxxxx>
Cc: Dave Safford <safford@xxxxxxxxxx>
Cc: Mimi Zohar <zohar@xxxxxxxxxx>
Cc: Serge Hallyn <sergeh@xxxxxxxxxx>
Cc: Chris Wright <chrisw@xxxxxxxxxxxx>
Cc: Stephen Smalley <sds@xxxxxxxxxxxxx>
Cc: James Morris <jmorris@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
security/slim/Kconfig | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN security/slim/Kconfig~panic-on-slim-selinux security/slim/Kconfig
--- a/security/slim/Kconfig~panic-on-slim-selinux
+++ a/security/slim/Kconfig
@@ -1,6 +1,6 @@
config SECURITY_SLIM
boolean "SLIM support"
- depends on SECURITY && SECURITY_NETWORK && INTEGRITY
+ depends on SECURITY && SECURITY_NETWORK && INTEGRITY && !SECURITY_SELINUX
help
The Simple Linux Integrity Module implements a modified low water-mark
mandatory access control integrity model.
_
Patches currently in -mm which might be from dwalker@xxxxxxxxxx are
origin.patch
slim-make-and-config-stuff.patch
panic-on-slim-selinux.patch
profile-likely-unlikely-macros.patch
profile_likely-export-do_check_likely.patch
profile-likely-unlikely-macros_remove-likely-profiling-int-cast.patch
profile-likely-unlikely-macros-x86_64-fix.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
