From: Segher Boessenkool <segher@kernel.crashing.org>
To: Marco Elver <elver@google.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
llvm@lists.linux.dev,
LSM List <linux-security-module@vger.kernel.org>,
linux-toolchains@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Kees Cook <keescook@chromium.org>,
Mark Brown <broonie@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Andrew Morton <akpm@linux-foundation.org>,
Vipin Sharma <vipinsh@google.com>,
Chris Down <chris@chrisdown.name>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Daniel Borkmann <daniel@iogearbox.net>,
Vlastimil Babka <vbabka@suse.cz>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Revert "Enable '-Werror' by default for all kernel builds"
Date: Tue, 7 Sep 2021 17:42:27 -0500 [thread overview]
Message-ID: <20210907224227.GL1583@gate.crashing.org> (raw)
In-Reply-To: <YTfkO2PdnBXQXvsm@elver.google.com>
On Wed, Sep 08, 2021 at 12:14:19AM +0200, Marco Elver wrote:
> Here's a datapoint: I had to disable CONFIG_WERROR on a bunch of syzbot
> instances which started failing because of -Werror [1], because syzbot's
> time is better spent on fuzzing, and having the odd warning in some
> subsystem penalize fuzzing of the entire kernel is not appropriate.
Similarly, I have to disable -Werror (which various archs and subsystems
already use) whenever I test building the kernel with new toolchains.
It is the biggest set of kernel patches I keep, already, since many
years.
I actually have good hopes that a centralised -Werror thing will make
this easier :-)
Maybe there can be an E=[01] kernel build flag to disable / enable
CONFIG_WERROR? Something that will override it for just that command.
This would make life easier for many use cases, while at the same time
not being something that people can "forget" they did.
Segher
next prev parent reply other threads:[~2021-09-07 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 18:38 [PATCH] Revert "Enable '-Werror' by default for all kernel builds" Nick Desaulniers
2021-09-07 18:55 ` Fāng-ruì Sòng
2021-09-07 19:16 ` Linus Torvalds
2021-09-07 20:30 ` Nick Desaulniers
2021-09-07 22:14 ` Marco Elver
2021-09-07 22:18 ` Linus Torvalds
2021-09-07 22:33 ` Randy Dunlap
2021-09-13 9:32 ` Pavel Machek
2021-09-13 9:46 ` Greg Kroah-Hartman
2021-09-13 10:02 ` Pavel Machek
2021-09-13 10:51 ` Greg Kroah-Hartman
2021-09-20 16:26 ` Geert Uytterhoeven
2021-09-13 9:50 ` Florian Weimer
2021-09-13 17:42 ` Linus Torvalds
2021-09-13 14:33 ` Guenter Roeck
2021-09-07 22:28 ` Guenter Roeck
2021-09-07 22:42 ` Segher Boessenkool [this message]
2021-09-07 22:55 ` Mark Brown
2021-09-07 23:00 ` Nathan Chancellor
2021-09-07 23:35 ` Mark Brown
2021-09-08 16:12 ` Steven Rostedt
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=20210907224227.GL1583@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=chris@chrisdown.name \
--cc=daniel@iogearbox.net \
--cc=elver@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=vipinsh@google.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;
as well as URLs for NNTP newsgroup(s).