From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: more build problems with "Makefile: move stackprotector availability out of Kconfig"
Date: Tue, 17 Oct 2017 19:52:06 +0100 [thread overview]
Message-ID: <20171017185206.dquho5wtr5f6pwmv@sirena.co.uk> (raw)
In-Reply-To: <CAK8P3a0Qa4dw_6WLsyjWFVXD3-DUa_2V=Yj9THvNE=wWMNH5VA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
On Tue, Oct 17, 2017 at 08:47:06PM +0200, Arnd Bergmann wrote:
> To clarify: with my gcc-4.9/gcc-5 build, -mstack-protector-guard=tls
> has no effect,
> the output is the same as with -mstack-protector-guard=global using the Ubuntu
> compilers of the same version.
Jumping in here... on IRC Arnd suggested reverting 123c48cf899d
("Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO") from -next. What
do you think Kees?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-10-17 18:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 11:00 more build problems with "Makefile: move stackprotector availability out of Kconfig" Arnd Bergmann
2017-10-17 15:20 ` Kees Cook
2017-10-17 15:23 ` Arnd Bergmann
2017-10-17 15:26 ` Kees Cook
2017-10-17 15:33 ` Arnd Bergmann
2017-10-17 15:34 ` Kees Cook
2017-10-17 15:52 ` Arnd Bergmann
2017-10-17 18:26 ` Kees Cook
2017-10-17 18:41 ` Arnd Bergmann
2017-10-17 18:47 ` Arnd Bergmann
2017-10-17 18:52 ` Mark Brown [this message]
2017-10-17 18:53 ` Kees Cook
2017-10-17 19:56 ` Andrew Morton
2017-10-17 20:04 ` Mark Brown
2017-10-17 20:06 ` Kees Cook
2017-10-19 0:41 ` Masahiro Yamada
2017-10-19 2:19 ` Kees Cook
2017-10-17 18:57 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171017185206.dquho5wtr5f6pwmv@sirena.co.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.