linux-kernel - Re: [PATCH 4.19 00/23] 4.19.40-stable 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: <20190505090236.GA24937@kroah.com>
Date:   Sun, 5 May 2019 11:02:36 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     open list <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Shuah Khan <shuah@...nel.org>, patches@...nelci.org,
        Ben Hutchings <ben.hutchings@...ethink.co.uk>,
        lkft-triage@...ts.linaro.org,
        linux- stable <stable@...r.kernel.org>
Subject: Re: [PATCH 4.19 00/23] 4.19.40-stable review

On Sun, May 05, 2019 at 02:23:22PM +0530, Naresh Kamboju wrote:
> On Sun, 5 May 2019 at 12:38, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > On Sat, May 04, 2019 at 10:00:44PM -0500, Dan Rue wrote:
> > > On Sat, May 04, 2019 at 12:25:02PM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 4.19.40 release.
> > > > There are 23 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 Mon 06 May 2019 10:24:19 AM UTC.
> > > > Anything received after that time might be too late.
> > >
> > >
> > > Results from Linaro’s test farm.
> > > Regressions detected.
> >
> > Really?  Where?
> 
> Not really.
> selftest: net: msg_zerocopy.sh is an intermittent failure on qemu_i386 device.

Is that a test problem, or a qemu problem?

> We could ignore this failure as known issues.

It wasn't listed in the report, or did I miss it?