linux-kernel - Re: -Werror for `make W=0`

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHp75VcKpkZQ78xygzWTQhNsy8aLBzKzqVJTtzygzTYnWeqmyQ@mail.gmail.com>
Date:   Wed, 19 Aug 2020 14:50:07 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Arvind Sankar <nivedita@...m.mit.edu>,
        Ard Biesheuvel <ardb@...nel.org>,
        Dmitry Vyukov <dvyukov@...gle.com>, X86 ML <x86@...nel.org>,
        David Laight <David.Laight@...lab.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: -Werror for `make W=0`

On Wed, Aug 19, 2020 at 1:48 PM Masahiro Yamada <masahiroy@...nel.org> wrote:
> On Wed, Aug 19, 2020 at 6:44 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> >
> > Hi!
> >
> > Maybe silly idea, but would it make sense to enable -Werror for default warning
> > level, let's say W=0, at some point?
> >
>
> Every GCC release adds new warning options.
>
> Enabling -Werror by default means
> the kernel build is suddenly broken
> with new compilers, correct?

Probably, and at the same time we keep our hand on the pulse of the
changes, right?
Adding those warnings to W=1, 2, ... block might be not the bad idea after all.

Maybe some flag CONFIG_DEBUG_WERROR ? Then CIs or other early stage
users can enable by default and be informed.

-- 
With Best Regards,
Andy Shevchenko