linux-kernel - Re: stable-rc build: 6 warnings 0 failures (stable-rc/v3.18.72-22-g11fceae)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK8P3a2_=bBP1cyoSgU9PvFs_iUhofbFoOjMMU0tD3o=dV6F_g@mail.gmail.com>
Date:   Fri, 6 Oct 2017 11:12:32 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     gregkh <gregkh@...uxfoundation.org>
Cc:     "Olof's autobuilder" <build@...om.net>,
        stable <stable@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Olof Johansson <olof@...om.net>,
        Kernel Build Reports Mailman List 
        <kernel-build-reports@...ts.linaro.org>
Subject: Re: stable-rc build: 6 warnings 0 failures (stable-rc/v3.18.72-22-g11fceae)

On Thu, Oct 5, 2017 at 11:16 AM, gregkh <gregkh@...uxfoundation.org> wrote:
> On Wed, Oct 04, 2017 at 09:31:25PM +0200, Arnd Bergmann wrote:
>> On Tue, Oct 3, 2017 at 2:25 PM, Olof's autobuilder <build@...om.net> wrote:
>>
>> > Warnings:
>> >
>> >       2 drivers/media/pci/ttpci/av7110_hw.h:406:3: warning: 'memcpy': specified size between 18446744071562067968 and 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
>>
>> This was fixed in linux-4.11:
>>
>> 69d3973af1ac ("[media] ttpci: address stringop overflow warning")
>>
>> >       4 drivers/staging/nvec/nvec_ps2.c:168:14: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
>>
>> and this was fixed in linux-4.2:
>>
>> 716baa7b430c ("staging: nvec: remove duplicated const")
>>
>> Both warnings show up for Olof's build bot in 3.18, but the fixes should
>> also apply to the later kernels.
>
> Thanks for these, all now queued up.

It looks like you applied them to 4.4.y and 4.9.y, but not to 3.18.y, which
still shows both problems in the 3.18.73 build report.

Can you check again?

Thanks,

       Arnd