[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20180305111708.GA4156@pjb1027-Latitude-E5410>
Date: Mon, 5 Mar 2018 20:17:08 +0900
From: Jinbum Park <jinb.park7@...il.com>
To: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel-hardening@...ts.openwall.com
Cc: gregkh@...uxfoundation.org, tglx@...utronix.de,
kstewart@...uxfoundation.org, luto@...capital.net,
dsafonov@...tuozzo.com, keescook@...omium.org, will.deacon@....com,
mark.rutland@....com, danielmicay@...il.com, arnd@...db.de,
catalin.marinas@....com
Subject: [PATCH v2 0/2] arm: Add ARCH_HAS_FORTIFY_SOURCE
Hi,
This patch series are to select ARCH_HAS_FORTIFY_SOUCE on arm.
A lot of architectures already select ARCH_HAS_FORTIFY_SOURCE
to support CONFIG_FORTIFY_SOURCE that detects overflows at compile-time.
(6974f0c4555e ("include/linux/string.h:
add the option of fortified string.h functions)
ARM can be built and run with CONFIG_FORTIFY_SOURCE.
Additionally, modify vdso.c to remove compile-error that happens
when built arm kernel with CONFIG_FORTIFY_SOURCE.
v2 :
Fix build error reported by kbuild test robot.
- Add fortify_panic() in arch/arm/boot/compressed/misc.c,
because arch/arm/boot/compressed/* can't find that function.
Jinbum Park (2):
arm: mm: Define vdso_start, vdso_end as array
arm: Kconfig: Add ARCH_HAS_FORTIFY_SOURCE
arch/arm/Kconfig | 1 +
arch/arm/include/asm/vdso.h | 2 --
arch/arm/kernel/vdso.c | 12 +++++++-----
3 files changed, 8 insertions(+), 7 deletions(-)
--
1.9.1
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
