Re: [RESEND][PATCH] kbuild: Abort build on bad stack protector flag

2016-07-26 Thread Kees Cook
On Tue, Jul 26, 2016 at 2:06 PM, Michal Marek wrote: > On Tue, Jul 12, 2016 at 03:30:43PM -0700, Kees Cook wrote: >> Before, the stack protector flag was sanity checked before .config had >> been reprocessed. This meant the build couldn't be aborted early, and >> only a warning

Re: [RESEND][PATCH] kbuild: Abort build on bad stack protector flag

2016-07-26 Thread Kees Cook
On Tue, Jul 26, 2016 at 2:06 PM, Michal Marek wrote: > On Tue, Jul 12, 2016 at 03:30:43PM -0700, Kees Cook wrote: >> Before, the stack protector flag was sanity checked before .config had >> been reprocessed. This meant the build couldn't be aborted early, and >> only a warning could be emitted

Re: [RESEND][PATCH] kbuild: Abort build on bad stack protector flag

2016-07-26 Thread Michal Marek
On Tue, Jul 12, 2016 at 03:30:43PM -0700, Kees Cook wrote: > Before, the stack protector flag was sanity checked before .config had > been reprocessed. This meant the build couldn't be aborted early, and > only a warning could be emitted followed later by the compiler blowing > up with an unknown

Re: [RESEND][PATCH] kbuild: Abort build on bad stack protector flag

2016-07-26 Thread Michal Marek
On Tue, Jul 12, 2016 at 03:30:43PM -0700, Kees Cook wrote: > Before, the stack protector flag was sanity checked before .config had > been reprocessed. This meant the build couldn't be aborted early, and > only a warning could be emitted followed later by the compiler blowing > up with an unknown

[RESEND][PATCH] kbuild: Abort build on bad stack protector flag

2016-07-12 Thread Kees Cook
Before, the stack protector flag was sanity checked before .config had been reprocessed. This meant the build couldn't be aborted early, and only a warning could be emitted followed later by the compiler blowing up with an unknown flag. This has caused a lot of confusion over time, so this splits

[RESEND][PATCH] kbuild: Abort build on bad stack protector flag

2016-07-12 Thread Kees Cook
Before, the stack protector flag was sanity checked before .config had been reprocessed. This meant the build couldn't be aborted early, and only a warning could be emitted followed later by the compiler blowing up with an unknown flag. This has caused a lot of confusion over time, so this splits