linux-kernel - Re: next/master boot bisection: next-20190617 on sun8i-h2-plus-orangepi-zero

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: <7d0a9da1-0b42-d4e9-0690-32d58a6d27de@collabora.com>
Date:   Tue, 18 Jun 2019 21:53:41 +0100
From:   Guillaume Tucker <guillaume.tucker@...labora.com>
To:     Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
        Kevin Hilman <khilman@...libre.com>
Cc:     "David S. Miller" <davem@...emloft.net>,
        tomeu.vizoso@...labora.com, mgalka@...labora.com,
        broonie@...nel.org, matthew.hart@...aro.org,
        enric.balletbo@...labora.com, Jose Abreu <joabreu@...opsys.com>,
        Giuseppe Cavallaro <peppe.cavallaro@...com>,
        Alexandre Torgue <alexandre.torgue@...com>,
        Linus Walleij <linus.walleij@...aro.org>,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Andrew Lunn <andrew@...n.ch>,
        linux-stm32@...md-mailman.stormreply.com,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: next/master boot bisection: next-20190617 on
 sun8i-h2-plus-orangepi-zero

On 18/06/2019 21:42, Martin Blumenstingl wrote:
> On Tue, Jun 18, 2019 at 6:53 PM Kevin Hilman <khilman@...libre.com> wrote:
> [...]
>> This seems to have broken on several sunxi SoCs, but also a MIPS SoC
>> (pistachio_marduk):
>>
>> https://storage.kernelci.org/next/master/next-20190618/mips/pistachio_defconfig/gcc-8/lab-baylibre-seattle/boot-pistachio_marduk.html
> today I learned why initializing arrays on the stack is important
> too bad gcc didn't warn that I was about to shoot myself (or someone
> else) in the foot :/
> 
> I just sent a fix: [0]
> 
> sorry for this issue and thanks to Kernel CI for even pointing out the
> offending commit (this makes things a lot easier than just yelling
> that "something is broken")

Glad that helped :)

If you would be so kind as to credit our robot friend in your
patch, it'll be forever grateful:

  Reported-by: "kernelci.org bot" <bot@...nelci.org>

Thanks,
Guillaume

> Martin
> 
> 
> [0] https://patchwork.ozlabs.org/patch/1118313/
>