public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Masahiro Yamada <masahiroy@kernel.org>,
	linux-hardening@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@kernel.org>
Subject: Re: [PATCH] gcc-plugins: Disable GCC_PLUGIN_CYC_COMPLEXITY for s390
Date: Tue, 23 Feb 2021 10:17:14 -0800	[thread overview]
Message-ID: <202102231016.F212B396@keescook> (raw)
In-Reply-To: <YDVDg/EZWjCZQn2v@osiris>

On Tue, Feb 23, 2021 at 07:03:47PM +0100, Heiko Carstens wrote:
> Well, if we would have e.g. RANDCONFIG, then we could probably revert
> 334ef6ed06fa ("init/Kconfig: make COMPILE_TEST depend on !S390") and
> instead let COMPILE_TEST depend on !RANDCONFIG.
> I think this _could_ solve all common problems we currently see.
> 
> And it would also do what you suggested.

I've wanted similar (e.g. for some UBSAN options that would go weird
under RANDCONFIG). :)

-- 
Kees Cook

  reply	other threads:[~2021-02-23 18:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 22:56 [PATCH] gcc-plugins: Disable GCC_PLUGIN_CYC_COMPLEXITY for s390 Guenter Roeck
2021-02-22 12:05 ` Heiko Carstens
2021-02-22 15:18   ` Guenter Roeck
2021-02-22 15:45     ` Masahiro Yamada
2021-02-22 16:03       ` Guenter Roeck
2021-02-23 11:54         ` Heiko Carstens
2021-02-23 17:41           ` Guenter Roeck
2021-02-23 18:03             ` Heiko Carstens
2021-02-23 18:17               ` Kees Cook [this message]
2021-02-24  1:46               ` Guenter Roeck
2021-02-24 14:19                 ` Masahiro Yamada

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=202102231016.F212B396@keescook \
    --to=keescook@chromium.org \
    --cc=arnd@kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=masahiroy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox