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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 5 Sep 2021 11:21:49 -0700
From:   Linus Torvalds <>
To:     Kees Cook <>
Cc:     Linux Kernel Mailing List <>,
        Arnd Bergmann <>, Daniel Vetter <>,
        Dan Williams <>,
        Rasmus Villemoes <>,
        Greg Kroah-Hartman <>,
        "Gustavo A. R. Silva" <>,
        Keith Packard <>,
        Nathan Chancellor <>,
        Nick Desaulniers <>,
Subject: Re: [GIT PULL] overflow updates for v5.15-rc1

On Sun, Sep 5, 2021 at 10:36 AM Linus Torvalds
<> wrote:
> Sadly, I don't think linux-next checks for warnings.
> I really want to enable -Werror at some point, but every time I think
> I should, I just end up worrying about another random new compiler (or
> a random old one).
> We do have -Werror in various configurations (and in some sub-trees).

Whatever. I'll just make a new config option, make it 'default y', and
it will be on for anybody doing allmodconfig builds etc.

And if people have new compilers, or odd configurations that still
cause warnings, they can turn it off, but hopefully this will make
compiler warnings in linux-next (or any other automated builds) cause
a lot more noise.


Powered by blists - more mailing lists