diff options
| author | Eric Paris <eparis@redhat.com> | 2008-06-09 20:51:37 (GMT) |
|---|---|---|
| committer | James Morris <jmorris@namei.org> | 2008-07-14 05:02:00 (GMT) |
| commit | 6cbe27061a69ab89d25dbe42d1a4f33a8425fe88 (patch) | |
| tree | 883e50c699dcd495ca9fc985e71622394ce21001 /security/selinux/selinuxfs.c | |
| parent | 22df4adb049a5cbb340dd935f5bbfa1ab3947562 (diff) | |
| download | linux-fsl-qoriq-6cbe27061a69ab89d25dbe42d1a4f33a8425fe88.tar.xz | |
SELinux: more user friendly unknown handling printk
I've gotten complaints and reports about people not understanding the
meaning of the current unknown class/perm handling the kernel emits on
every policy load. Hopefully this will make make it clear to everyone
the meaning of the message and won't waste a printk the user won't care
about anyway on systems where the kernel and the policy agree on
everything.
Signed-off-by: Eric Paris <eparis@redhat.com>
Signed-off-by: James Morris <jmorris@namei.org>
Diffstat (limited to 'security/selinux/selinuxfs.c')
| -rw-r--r-- | security/selinux/selinuxfs.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/security/selinux/selinuxfs.c b/security/selinux/selinuxfs.c index 07a5db6..69c9dcc 100644 --- a/security/selinux/selinuxfs.c +++ b/security/selinux/selinuxfs.c @@ -356,11 +356,6 @@ static ssize_t sel_write_load(struct file *file, const char __user *buf, length = count; out1: - - printk(KERN_INFO "SELinux: policy loaded with handle_unknown=%s\n", - (security_get_reject_unknown() ? "reject" : - (security_get_allow_unknown() ? "allow" : "deny"))); - audit_log(current->audit_context, GFP_KERNEL, AUDIT_MAC_POLICY_LOAD, "policy loaded auid=%u ses=%u", audit_get_loginuid(current), |