linux-kernel - RE: [PATCH 4.19 00/56] 4.19.137-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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <OSAPR01MB23857AEF0D818484DF9BAEF3B74A0@OSAPR01MB2385.jpnprd01.prod.outlook.com>
Date:   Tue, 4 Aug 2020 14:53:45 +0000
From:   Chris Paterson <Chris.Paterson2@...esas.com>
To:     Pavel Machek <pavel@...x.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "linux@...ck-us.net" <linux@...ck-us.net>,
        "shuah@...nel.org" <shuah@...nel.org>,
        "patches@...nelci.org" <patches@...nelci.org>,
        "ben.hutchings@...ethink.co.uk" <ben.hutchings@...ethink.co.uk>,
        "lkft-triage@...ts.linaro.org" <lkft-triage@...ts.linaro.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [PATCH 4.19 00/56] 4.19.137-rc1 review

Hi Pavel,

> From: stable-owner@...r.kernel.org <stable-owner@...r.kernel.org> On
> Behalf Of Pavel Machek
> Sent: 04 August 2020 08:46
>
> *** gpg4o | The signature of this email could not be verified because the
> following public key is missing. Click here to search and import the key
> 30E7F06A95DBFAF2 ***
>
> Hi!
>
> > This is the start of the stable review cycle for the 4.19.137 release.
> > There are 56 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, 05 Aug 2020 12:18:33 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> >     https://www.kernel.org/pub/linux/kernel/v4.x/stable-
> review/patch-4.19.137-rc1.gz
> > or in the git tree and branch at:
> >     git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-
> rc.git linux-4.19.y
> > and the diffstat can be found below.
>
> CIP test farm does not see any problems...
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-
> /pipelines/173700523
>
> ...except that one of the targets is unavailable.

This is up again now so I've rescheduled the tests.

>
> Chris, could we get distinction between "we ran a test and it failed"
> and "we could not run a test because mice ate the cables"?

You can see that the board is offline in the GitLab CI log, but that's not ideal.
I can change it so the job passes with a nice big green tick, but this may lead people to think that the tests had actually been run.
Maybe we need a yellow icon in the GitLab GUI for this circumstance. Looks like we aren't the first with this request:
https://gitlab.com/gitlab-org/gitlab/-/issues/16733

Kind regards, Chris 

>
> Best regards,
>                                                                       Pavel
>
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures)
> http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html