linux-kernel - Re: Warnings whilst building 5.2.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] [day] [month] [year] [list]

Message-ID: <d1413ca8-23e2-3f77-cd57-87b4229627aa@nvidia.com>
Date:   Tue, 6 Aug 2019 23:45:00 -0700
From:   John Hubbard <jhubbard@...dia.com>
To:     Chris Clayton <chris2553@...glemail.com>,
        "Enrico Weigelt, metux IT consult" <lkml@...ux.net>,
        LKML <linux-kernel@...r.kernel.org>, <tglx@...utronix.de>,
        <hpa@...or.com>
CC:     Ingo Molnar <mingo@...hat.com>, "x86@...nel.org" <x86@...nel.org>,
        Borislav Petkov <bp@...en8.de>
Subject: Re: Warnings whilst building 5.2.0+

On 8/6/19 11:30 PM, Chris Clayton wrote:
> On 09/07/2019 12:39, Chris Clayton wrote:
>> On 09/07/2019 11:37, Enrico Weigelt, metux IT consult wrote:
>>> On 09.07.19 08:06, Chris Clayton wrote:
...
>>> Can you check older versions, too ? Maybe also trying older gcc ?
>>>
>>
>> I see the same warnings building linux-5.2.0 with gcc9. However, I don't see the warnings building linux-5.2.0 with the
>> the 20190705 of gcc8. So the warnings could result from an improvement (i.e. the problem was in the kernel, but
>> undiscovered by gcc8) or from a regression in gcc9.
>>
> 
>  From the discussion starting at https://marc.info/?l=linux-kernel&m=156401014023908, it would appear that the problem is
> undiscovered by gcc8. Building a fresh pull of Linus' tree this morning (v5.3-rc3-282-g33920f1ec5bf), I see that the
> warnings are still being emitted. Adding the participants in the other discussion to this one.
> 

The warnings are still there because the fix has not been committed to any
tree yet.

If you could try out my proposed fix [1], and reply to that thread with perhaps a
Tested-by tag, that would help encourage the maintainers to accept it.

So far it hasn't made it to the top of their inboxes, but I'm hoping... :)


[1] https://lore.kernel.org/r/20190731054627.5627-2-jhubbard@nvidia.com
     ("x86/boot: save fields explicitly, zero out everything else")

thanks,
-- 
John Hubbard
NVIDIA