[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1497903987-21002-6-git-send-email-keescook@chromium.org>
Date: Mon, 19 Jun 2017 13:26:25 -0700
From: Kees Cook <keescook@...omium.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Kees Cook <keescook@...omium.org>, Daniel Axtens <dja@...ens.net>,
Daniel Micay <danielmicay@...il.com>,
linux-kernel@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: [PATCH 5/7] powerpc: Don't fortify prom_init
From: Daniel Axtens <dja@...ens.net>
prom_init is a bit special; in theory it should be able to be
linked separately to the kernel. To keep this from getting too
complex, the symbols that prom_init.c uses are checked.
Fortification adds symbols, and it gets quite messy as it includes
things like panic(). So just don't fortify prom_init.c for now.
Cc: Kees Cook <keescook@...omium.org>
Cc: Daniel Micay <danielmicay@...il.com>
Signed-off-by: Daniel Axtens <dja@...ens.net>
Acked-by: Michael Ellerman <mpe@...erman.id.au>
Signed-off-by: Kees Cook <keescook@...omium.org>
---
arch/powerpc/kernel/prom_init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
index dd8a04f3053a..613f79f03877 100644
--- a/arch/powerpc/kernel/prom_init.c
+++ b/arch/powerpc/kernel/prom_init.c
@@ -15,6 +15,9 @@
#undef DEBUG_PROM
+/* we cannot use FORTIFY as it brings in new symbols */
+#define __NO_FORTIFY
+
#include <stdarg.h>
#include <linux/kernel.h>
#include <linux/string.h>
--
2.7.4
Powered by blists - more mailing lists