linux-kernel - Re: linux-next: Tree for Jul 10

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: <31e99bdc-1243-3be7-74aa-59c01820ed8e@infradead.org>
Date:   Sun, 12 Jul 2020 19:26:15 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Andy Shevchenko <andriy.shevchenko@...el.com>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: linux-next: Tree for Jul 10

On 7/12/20 7:19 PM, Randy Dunlap wrote:
> On 7/12/20 3:01 PM, Stephen Rothwell wrote:
>> Hi Andy,
>>
>> On Sun, 12 Jul 2020 18:56:04 +0300 Andy Shevchenko <andriy.shevchenko@...el.com> wrote:
>>>
>>> On Fri, Jul 10, 2020 at 06:33:18PM +1000, Stephen Rothwell wrote:
>>>>
>>>> Changes since 20200709:
>>>
>>> I can't build it on Debian with Sparse enabled
>>>
>>> CC      init/main.o
>>> init/main.c:760:20: warning: no previous prototype for ‘mem_encrypt_init’ [-Wmissing-prototypes]
>>> 760 | void __init __weak mem_encrypt_init(void) { }
>>> |                    ^~~~~~~~~~~~~~~~
>>> CHECK   /home/andy/prj/linux-topic-uart/init/main.c
>>> include/linux/compiler.h:309:16: error: typename in expression
>>> include/linux/compiler.h:309:16: error: Expected ) in function call
>>> include/linux/compiler.h:309:16: error: got :
>>> ...
>>> (All READ_ONCE() entries fail)
>>>
>>> Is it known issue?
>>
>> Not that I am aware of at the moment.  Does next-20200709 work?  Does
>> Linus' tree work?  The only obvious thing I can think of is commit
> 
> I'm hitting this same thing on 5.8-rc5. (x86_64)
> 
> 
>> 6ec4476ac825 ("Raise gcc version requirement to 4.9")
>>
>> The commmit message says:
>>
>>     Using _Generic also means that you will need to have a very recent
>>     version of 'sparse', but thats easy to build yourself, and much less of
>>     a hassle than some old gcc version can be.

OK, no problems, newer sparse fixes it.

-- 
~Randy