From: Philipp Rudo <pr...@linux.ibm.com>

BugLink: https://bugs.launchpad.net/bugs/1843961

Kernel lock down isn't initalized in common but in arch code. So
initialize it for s390 as well.

Signed-off-by: Philipp Rudo <pr...@linux.ibm.com>
Signed-off-by: Dimitri John Ledkov <x...@ubuntu.com>
---
 arch/s390/kernel/setup.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/s390/kernel/setup.c b/arch/s390/kernel/setup.c
index 253177900950..2ba122f1dd4f 100644
--- a/arch/s390/kernel/setup.c
+++ b/arch/s390/kernel/setup.c
@@ -49,6 +49,7 @@
 #include <linux/memory.h>
 #include <linux/compat.h>
 #include <linux/start_kernel.h>
+#include <linux/security.h>
 
 #include <asm/boot_data.h>
 #include <asm/ipl.h>
@@ -1107,6 +1108,7 @@ void __init setup_arch(char **cmdline_p)
                pr_info("Linux is running as a guest in 64-bit mode\n");
 
        log_component_list();
+       init_lockdown();
 
        /* Have one command line that is parsed and saved in /proc/cmdline */
        /* boot_command_line has been already set up in early.c */
-- 
2.20.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843961

Title:
  s390/setup: Actually init kernel lock down

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843961/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to