From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Jann Horn <jannh@google.com>
Cc: Kees Cook <keescook@chromium.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Russell King <linux@armlinux.org.uk>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Emese Revfy <re.emese@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default
Date: Fri, 14 Jun 2019 18:12:43 +0200 [thread overview]
Message-ID: <20190614181243.4430f0d4@primarylaptop.localdomain> (raw)
In-Reply-To: <CAG48ez30+VOj78rCiWMKtm0tHdVR67CcrHVCV-FFCfK-nRQTOw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 316 bytes --]
On Fri, 14 Jun 2019 18:05:19 +0200
Jann Horn <jannh@google.com> wrote:
[...]
> STACKPROTECTOR_PER_TASK defaults to y and depends on GCC_PLUGINS, so
> is that perhaps what broke? Can you try whether disabling just that
> works for you?
I've tried that, and it's sufficient to make the device boot.
Denis.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-14 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190614145755.10926-1-GNUtoo@cyberdimension.org>
2019-06-14 16:05 ` [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default Jann Horn
2019-06-14 16:12 ` Denis 'GNUtoo' Carikli [this message]
2019-06-14 16:28 ` Russell King - ARM Linux admin
2019-06-14 18:14 ` Denis 'GNUtoo' Carikli
2019-06-14 18:54 ` Russell King - ARM Linux admin
2019-06-15 10:13 ` Paul Kocialkowski
2019-06-21 23:42 ` Denis 'GNUtoo' Carikli
2019-06-24 13:31 ` Paul Kocialkowski
2019-06-15 3:08 ` 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=20190614181243.4430f0d4@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=paul.kocialkowski@bootlin.com \
--cc=re.emese@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox