linux-kernel - Re: sparse warnings in overflow.h

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: <20180607234533.nfdxd4cqiygahfms@ltop.local>
Date:   Fri, 8 Jun 2018 01:45:34 +0200
From:   Luc Van Oostenryck <luc.vanoostenryck@...il.com>
To:     Rasmus Villemoes <linux@...musvillemoes.dk>
Cc:     Kees Cook <keescook@...omium.org>, Miroslav Benes <mbenes@...e.cz>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: sparse warnings in overflow.h

On Thu, Jun 07, 2018 at 09:25:09PM +0200, Rasmus Villemoes wrote:
> 
> IIRC, the problem is that sparse pretends to be the gcc sparse itself
> was built with, which is obviously entirely unrelated to the C dialect
> that that particular sparse version groks. Sigh. Ack to the fix above.

Yes, indeed, and it is sometimes a problem.
Ideal would be that sparse would pretend to be same GCC as the one used
to compile the code being checked *and* to have exactly the same features.

Pretending to be an older version of GCC would maybe solve the present
problem it's not really a general solution.

One good thing would be to not depend on GCC versions to enable some
features (but GCC offers few facilities helping here).

Best regards,
-- Luc Van Oostenryck