linux-kernel - Re: [PATCH 4.19 000/170] 4.19.14-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: <20190110065207.GA17195@kroah.com>
Date:   Thu, 10 Jan 2019 07:52:07 +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.19 000/170] 4.19.14-stable review

On Wed, Jan 09, 2019 at 11:40:48AM -0800, Guenter Roeck wrote:
> On Wed, Jan 09, 2019 at 03:38:11PM +0100, Greg Kroah-Hartman wrote:
> > On Tue, Jan 08, 2019 at 03:07:31PM -0800, Guenter Roeck wrote:
> > > On Mon, Jan 07, 2019 at 01:30:27PM +0100, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 4.19.14 release.
> > > > There are 170 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 Jan  9 10:43:54 UTC 2019.
> > > > Anything received after that time might be too late.
> > > > 
> > > 
> > > For v4.19.13-171-gc68ce175c3b8:
> > > 
> > > Build results:
> > > 	total: 155 pass: 152 fail: 3
> > > Failed builds: 
> > > 	powerpc:ppc64e_defconfig 
> > > 	powerpc:cell_defconfig 
> > > 	powerpc:maple_defconfig 
> > > Qemu test results:
> > > 	total: 332 pass: 319 fail: 13
> > > Failed tests: 
> > > 	ppc64:mac99:ppc64_book3s_defconfig:nosmp:initrd 
> > > 	ppc64:mac99:ppc64_book3s_defconfig:smp:initrd 
> > > 	ppc64:mac99:ppc64_book3s_defconfig:smp:ide:rootfs 
> > > 	ppc64:mac99:ppc64_book3s_defconfig:smp:mmc:rootfs 
> > > 	ppc64:mac99:ppc64_book3s_defconfig:smp:nvme:rootfs 
> > > 	ppc64:mac99:ppc64_book3s_defconfig:smp:scsi[DC395]:rootfs 
> > > 	ppc64:mpc8544ds:ppc64_e5500_defconfig:nosmp:initrd 
> > > 	ppc64:mpc8544ds:ppc64_e5500_defconfig:smp:initrd 
> > > 	ppc64:ppce500:corenet64_smp_defconfig:e5500:initrd 
> > > 	ppc64:ppce500:corenet64_smp_defconfig:e5500:nvme:rootfs 
> > > 	ppc64:ppce500:corenet64_smp_defconfig:e5500:mmc:rootfs 
> > > 	ppc64:ppce500:corenet64_smp_defconfig:e5500:scsi[53C895A]:rootfs
> > > 	ppc64:ppce500:corenet64_smp_defconfig:e5500:sata-sii3112:rootfs
> > 
> > Ugh, I thought this was just the cell build, didn't realize it hit more.
> > 
> > Ok, I've dropped the patch from all queues.  Odd that it only causes
> > problems on 4.19.y :(
> > 
> I don't know what you dropped, but v4.19.14 fails to build with 
> the same error. Did you drop it after the release ?

No, I should have dropped it before the release.  Let me go see what I
messed up...