Arnd Bergmann 7616ac70d1 apparmor: fix SECURITY_APPARMOR_HASH_DEFAULT parameter handling ... The newly added Kconfig option could never work and just causes a build error when disabled: security/apparmor/lsm.c:675:25: error: 'CONFIG_SECURITY_APPARMOR_HASH_DEFAULT' undeclared here (not in a function) bool aa_g_hash_policy = CONFIG_SECURITY_APPARMOR_HASH_DEFAULT; The problem is that the macro undefined in this case, and we need to use the IS_ENABLED() helper to turn it into a boolean constant. Another minor problem with the original patch is that the option is even offered in sysfs when SECURITY_APPARMOR_HASH is not enabled, so this also hides the option in that case. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Fixes: 6059f71f1e ("apparmor: add parameter to control whether policy hashing is used") Signed-off-by: John Johansen <john.johansen@canonical.com> Signed-off-by: James Morris <james.l.morris@oracle.com>		2016-07-27 17:39:26 +10:00
..
include	apparmor: fix module parameters can be changed after policy is locked	2016-07-12 08:43:10 -07:00
.gitignore
apparmorfs.c	apparmor: use list_next_entry instead of list_entry_next	2016-07-12 08:43:10 -07:00
audit.c
capability.c
context.c
crypto.c	apparmor: fix SECURITY_APPARMOR_HASH_DEFAULT parameter handling	2016-07-27 17:39:26 +10:00
domain.c	apparmor: ensure the target profile name is always audited	2016-07-12 08:43:10 -07:00
file.c
ipc.c
Kconfig	apparmor: add parameter to control whether policy hashing is used	2016-07-12 08:43:10 -07:00
lib.c
lsm.c	apparmor: fix SECURITY_APPARMOR_HASH_DEFAULT parameter handling	2016-07-27 17:39:26 +10:00
Makefile
match.c	apparmor: do not expose kernel stack	2016-07-12 08:43:10 -07:00
path.c
policy.c	apparmor: fix module parameters can be changed after policy is locked	2016-07-12 08:43:10 -07:00
policy_unpack.c	apparmor: fix SECURITY_APPARMOR_HASH_DEFAULT parameter handling	2016-07-27 17:39:26 +10:00
procattr.c
resource.c	apparmor: allow SYS_CAP_RESOURCE to be sufficient to prlimit another task	2016-07-12 08:43:10 -07:00
sid.c