linux-kernel - Re: [PATCH 4.19 000/264] 4.19.153-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]

Date:   Sat, 31 Oct 2020 10:45:00 +0100
From:   Salvatore Bonaccorso <carnil@...ian.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, pavel@...x.de, stable@...r.kernel.org
Subject: Re: [PATCH 4.19 000/264] 4.19.153-rc1 review

Hi Greg,

On Wed, Oct 28, 2020 at 12:56:19PM -0700, Guenter Roeck wrote:
> Retry.
> 
> On Wed, Oct 28, 2020 at 10:10:35AM -0700, Guenter Roeck wrote:
> > On Tue, Oct 27, 2020 at 02:50:58PM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.19.153 release.
> > > There are 264 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 Thu, 29 Oct 2020 13:53:47 +0000.
> > > Anything received after that time might be too late.
> > > 
> > 
> > Build results:
> > 	total: 155 pass: 152 fail: 3
> > Failed builds:
> > 	i386:tools/perf
> > 	powerpc:ppc6xx_defconfig
> > 	x86_64:tools/perf
> > Qemu test results:
> > 	total: 417 pass: 417 fail: 0
> > 
> > perf failures are as usual. powerpc:

Regarding the perf failures, do you plan to revert b801d568c7d8 ("perf
cs-etm: Move definition of 'traceid_list' global variable from header
file") included in 4.19.152 or is a bugfix underway?

Regards,
Salvatore