linux-kernel - Re: [PATCH 5.10 000/102] 5.10.21-rc1 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 for Android: free password hash cracker in your pocket

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

Message-ID: <YEURxE02KkuUYDTN@kroah.com>
Date:   Sun, 7 Mar 2021 18:47:48 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Pavel Machek <pavel@...x.de>
Cc:     Chris.Paterson2@...esas.com, linux-kernel@...r.kernel.org,
        torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, jonathanh@...dia.com,
        f.fainelli@...il.com, stable@...r.kernel.org
Subject: Re: [PATCH 5.10 000/102] 5.10.21-rc1 review

On Sun, Mar 07, 2021 at 06:18:25PM +0100, Pavel Machek wrote:
> Hi!
> 
> > > This is the start of the stable review cycle for the 5.10.21 release.
> > > There are 102 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.
> > 
> > Here situation is similar to 4.4
> > 
> > [   27.349919] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2017-5715 RESULT=fail>
> > Received signal: <TESTCASE> TEST_CASE_ID=CVE-2017-5715 RESULT=fail
> > 
> > So I see some kind of failure, and this time I suspect real kernel
> > problem.
> > 
> > https://lava.ciplatform.org/scheduler/job/171825
> > 
> > 4.19 has similar problem:
> > 
> > https://lava.ciplatform.org/scheduler/job/171812
> > 
> > Again, Ccing Chris, but it looks like something is wrong there.
> 
> It went away after I reran the tests, and the old tests failed due to
> timeout. So it looks like server with qemu was overloaded or something
> like that. There are still failures, but they are "boards not
> available" kind, so not a kernel problem.
> 
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.10.y
> 
> Tested-by: Pavel Machek (CIP) <pavel@...x.de>

Thanks for tracking this down and letting me know.

greg k-h