Re: move stack-protector availability out of Kconfig

2018-02-13 Thread Kees Cook
On Tue, Feb 13, 2018 at 7:27 AM, tedheadster wrote: > Kees, > I have a question about this patch. When I configure a kernel for > ARCH=i386 it sets these Kconfig variables this way: > > HAVE_CC_STACKPROTECTOR=y > CC_STACKPROTECTOR_AUTO=y > > CC_STACKPROTECTOR_NONE=n > CC_STACKPROTECTOR_REGULAR=n

Re: move stack-protector availability out of Kconfig

2018-02-13 Thread tedheadster
Kees, I have a question about this patch. When I configure a kernel for ARCH=i386 it sets these Kconfig variables this way: HAVE_CC_STACKPROTECTOR=y CC_STACKPROTECTOR_AUTO=y CC_STACKPROTECTOR_NONE=n CC_STACKPROTECTOR_REGULAR=n CC_STACKPROTECTOR_STRONG=n It seems to me that at least _one_ of th

[PATCH v2 2/3] Makefile: Move stack-protector availability out of Kconfig

2017-11-07 Thread Kees Cook
Various portions of the kernel, especially per-architecture pieces, need to know if the compiler is building with the stack protector. This was done in the arch/Kconfig with 'select', but this doesn't allow a way to do auto-detected compiler support. In preparation for creating an on-if-available d