diff options
author | 2020-03-08 20:57:51 -0400 | |
---|---|---|
committer | 2020-03-12 07:43:57 -0400 | |
commit | 9e2b4be377f0d715d9d910507890f9620cc22a9d (patch) | |
tree | b837793b54687af1ab19e7957833182399ff3d7d /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Merge branch 'next-integrity.logging-cleanup' into next-integrity (diff) | |
download | linux-dev-9e2b4be377f0d715d9d910507890f9620cc22a9d.tar.xz linux-dev-9e2b4be377f0d715d9d910507890f9620cc22a9d.zip |
ima: add a new CONFIG for loading arch-specific policies
Every time a new architecture defines the IMA architecture specific
functions - arch_ima_get_secureboot() and arch_ima_get_policy(), the IMA
include file needs to be updated. To avoid this "noise", this patch
defines a new IMA Kconfig IMA_SECURE_AND_OR_TRUSTED_BOOT option, allowing
the different architectures to select it.
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Nayna Jain <nayna@linux.ibm.com>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Acked-by: Philipp Rudo <prudo@linux.ibm.com> (s390)
Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions