linux-kernel - Re: mainline/master bisection: baseline.dmesg.crit on qemu

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: <b7d63093-a1a8-fbc1-6673-040d6ba8cc8d@collabora.com>
Date:   Thu, 16 Jul 2020 09:57:27 +0100
From:   Guillaume Tucker <guillaume.tucker@...labora.com>
To:     Sudeep Holla <sudeep.holla@....com>
Cc:     kernelci-results@...ups.io,
        Andre Przywara <andre.przywara@....com>,
        linux-arm-kernel@...ts.infradead.org,
        Rob Herring <robh+dt@...nel.org>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        devicetree@...r.kernel.org, Liviu Dudau <liviu.dudau@....com>,
        linux-kernel@...r.kernel.org
Subject: Re: mainline/master bisection: baseline.dmesg.crit on
 qemu_arm-vexpress-a15

On 06/07/2020 13:49, Sudeep Holla wrote:
> Hi,
> 
> On Sun, Jul 05, 2020 at 07:12:58PM -0700, kernelci.org bot wrote:
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>> * This automated bisection report was sent to you on the basis  *
>> * that you may be involved with the breaking commit it has      *
>> * found.  No manual investigation has been done to verify it,   *
>> * and the root cause of the problem may be somewhere else.      *
>> *                                                               *
>> * If you do send a fix, please include this trailer:            *
>> *   Reported-by: "kernelci.org bot" <bot@...nelci.org>          *
>> *                                                               *
>> * Hope this helps!                                              *
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>
> 
> Andre test and replied to one of the similar but earlier reports.
> Unless we get some response to that, we can't proceed and we can't
> do much other than ignoring these reports. Please respond to Andre's
> queries.


Sorry I missed your email, the regression is still there.  I'll
reply to André.

Guillaume