linux-kernel - Re: [PATCH 4.20 000/183] 4.20.13-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] [day] [month] [year] [list]

Date:   Wed, 27 Feb 2019 10:05:51 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 4.20 000/183] 4.20.13-stable review

On Tue, Feb 26, 2019 at 09:29:40AM -0800, Guenter Roeck wrote:
> On Mon, Feb 25, 2019 at 10:09:33PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.20.13 release.
> > There are 183 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 Feb 27 19:49:59 UTC 2019.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
> 	total: 171 pass: 169 fail: 2
> Failed builds: 
> 	powerpc:ppc6xx_defconfig 
> 	powerpc:86xx/sbc8641d_defconfig
> Qemu test results:
> 	total: 291 pass: 291 fail: 0
> 
> The build failure is:
> 
> In file included from arch/powerpc/kernel/ptrace.c:24:
> In function ‘user_regset_copyin’,
>     inlined from ‘vr_set’ at arch/powerpc/kernel/ptrace.c:490:9:
> include/linux/regset.h:258:4: error:
> 	‘memcpy’ offset [-527, -529] is out of the bounds [0, 16] of object ‘vrsave’ with type ‘union <anonymous>’ 
> 
> The problem is not new. It is seen now because I switched to use
> gcc 8.3.0. The problem is fixed in linux-next.

Ok, I'll ignore these powerpc build issues for now, thanks for testing
all of these and letting me know.

greg k-h