From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752335AbdFSU0i (ORCPT ); Mon, 19 Jun 2017 16:26:38 -0400 Received: from mail-pf0-f178.google.com ([209.85.192.178]:35928 "EHLO mail-pf0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752175AbdFSU0g (ORCPT ); Mon, 19 Jun 2017 16:26:36 -0400 From: Kees Cook To: Andrew Morton Cc: Kees Cook , Daniel Axtens , Daniel Micay , linux-kernel@vger.kernel.org, Stephen Rothwell Subject: [PATCH 5/7] powerpc: Don't fortify prom_init Date: Mon, 19 Jun 2017 13:26:25 -0700 Message-Id: <1497903987-21002-6-git-send-email-keescook@chromium.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1497903987-21002-1-git-send-email-keescook@chromium.org> References: <1497903987-21002-1-git-send-email-keescook@chromium.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Daniel Axtens 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 Cc: Daniel Micay Signed-off-by: Daniel Axtens Acked-by: Michael Ellerman Signed-off-by: Kees Cook --- 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 #include #include -- 2.7.4