linux-kernel - Re: [patch core/stackprotector] stackprotector: Fix build when compiler lacks support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Dec 2013 06:39:15 -0800
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	David Rientjes <rientjes@...gle.com>,
	Ingo Molnar <mingo@...nel.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	peterz@...radead.org, Andrew Morton <akpm@...ux-foundation.org>,
	linux@....linux.org.uk, ralf@...ux-mips.org, tglx@...utronix.de,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	james.hogan@...tec.com, Michal Marek <mmarek@...e.cz>,
	lethal@...ux-sh.org, shawn.guo@...aro.org,
	Kees Cook <keescook@...omium.org>, sfr@...b.auug.org.au,
	linux-kbuild@...r.kernel.org, linux-tip-commits@...r.kernel.org
Subject: Re: [patch core/stackprotector] stackprotector: Fix build when compiler
 lacks support

On 12/30/2013 1:37 PM, David Rientjes wrote:
> 8779657d29c0 ("stackprotector: Introduce CONFIG_CC_STACKPROTECTOR_STRONG")
> causes the build to break when the compiler doesn't support
> -fstack-protector-strong:
>
> 	cc1: error: unrecognized command line option ‘-fstack-protector-strong’
> 	cc1: error: unrecognized command line option ‘-fstack-protector-strong’
>
> with at least gcc 4.6.3.
>
> Instead of breaking the build, just warn of the failure and disable the
> feature.

ideally it also falls back to the less strict one, rather than not using stack protector at all...


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/