Re: [PATCH 4.19 000/170] 4.19.14-stable review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 1/10/19 5:17 AM, Greg Kroah-Hartman wrote:
On Thu, Jan 10, 2019 at 07:52:07AM +0100, Greg Kroah-Hartman wrote:
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...

I dropped e1c3743e1a20 ("powerpc/tm: Set MSR[TS] just prior to recheckpoint")
from the stable trees, which is what I was told was the commit that was
causing the problems by Christoph and Breno (on to: now).

Was that not the offending commit?  If so, what one was?

$ git describe
v4.19.14
groeck@server:~/src/linux-stable$ git log --oneline v4.19.13.. arch/powerpc/
a9935a127688 powerpc/tm: Unset MSR[TS] if not recheckpointing
34fc09193486 powerpc/fsl: Fix spectre_v2 mitigations reporting
groeck@server:~/src/linux-stable$

a9935a127688 is the culprit.

Guenter



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux