linux-kernel - Re: [PATCH] objtool: Don't use -Werror

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: <20190405162627.h3fadip7psc77zdf@vega.skynet.aixah.de>
Date:   Fri, 5 Apr 2019 18:26:27 +0200
From:   'Luis Ressel' <aranea@...ah.de>
To:     David Laight <David.Laight@...lab.com>
Cc:     Josh Poimboeuf <jpoimboe@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        open list <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] objtool: Don't use -Werror

On Fri, Apr 05, 2019 at 04:16:14PM +0000, David Laight wrote:

> In which case you should be looking at a way of removing -Wundef
> not removing -Werror.

No, my whole point is that this blacklisting approach doesn't work
outside a controlled dev environment, because different
compilers/compiler versions produce wildy different warnings.

I'm aware of several Linux distros which remove -Werror from build
systems whereever it is encountered. It's a well-known fact among
distributors that enabling -Werror for production builds is a bad idea.

Cheers,
Luis