linux-kernel - Re: [PATCH 4.14 00/54] 4.14.23-stable review

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: <d67ba57f-c6df-b854-9487-70ce95a321f9@roeck-us.net>
Date:   Tue, 27 Feb 2018 06:34:08 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Arnd Bergmann <arnd@...db.de>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, shuahkh@....samsung.com,
        patches@...nelci.org, ben.hutchings@...ethink.co.uk,
        lkft-triage@...ts.linaro.org, stable@...r.kernel.org
Subject: Re: [PATCH 4.14 00/54] 4.14.23-stable review

On 02/27/2018 05:08 AM, Greg Kroah-Hartman wrote:
> On Tue, Feb 27, 2018 at 02:59:39AM -0800, Guenter Roeck wrote:
>> On 02/26/2018 12:21 PM, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 4.14.23 release.
>>> There are 54 patches in this series, all will be posted as a response
>>> to this one.  If anyone has any issues with these being applied, please
>>> let me know.
>>>
>>> Responses should be made by Wed Feb 28 20:21:22 UTC 2018.
>>> Anything received after that time might be too late.
>>>
>>
>> microblaze, m32r:
>>
>> include/linux/byteorder/big_endian.h:8:2: warning: #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN [-Wcpp]
>>   #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN
>>    ^~~~~~~
>> /opt/buildbot/slave/stable-queue-4.14/build/lib/find_bit.c:176:15: error: redefinition of ‘find_next_zero_bit_le’
>>
>> v4.15 is also affected (m32r builds in v4.15, though, for some reason).
> 
> This sounds like Arnd's Kbuild change 101110f6271c ("Kbuild: always
> define endianess in kconfig.h")
> 
> Does this problem also show up in Linus's tree?
> 

No. My guess would be that some context patches are missing in the older kernels.

I also get lots of

include/linux/byteorder/big_endian.h:8:2: warning: #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN

which as it turns out is also seen in v4.14.22, meaning the actual problem
was most likely introduced earlier (I don't see that warning upstream).

Guenter