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
| ||
|
Date: Mon, 11 Jul 2016 21:16:24 -0700 From: Kevin Hilman <khilman@...libre.com> To: Guenter Roeck <linux@...ck-us.net> Cc: "kernelci.org bot" <bot@...nelci.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, shuah.kh@...sung.com, patches@...nelci.org, stable@...r.kernel.org Subject: Re: [PATCH 4.6 00/31] 4.6.4-stable review Guenter Roeck <linux@...ck-us.net> writes: > On Mon, Jul 11, 2016 at 01:04:35PM -0700, Kevin Hilman wrote: >> kernelci.org bot <bot@...nelci.org> writes: >> >> > stable-rc boot: 558 boots: 4 failed, 549 passed with 5 offline (v4.6.2-121-g6b5d7d0432d9) >> > >> > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.6.2-121-g6b5d7d0432d9/ >> > Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.6.2-121-g6b5d7d0432d9/ >> > >> > Tree: stable-rc >> > Branch: local/linux-4.6.y >> > Git Describe: v4.6.2-121-g6b5d7d0432d9 >> > Git Commit: 6b5d7d0432d9fe4c69436a289f96cce81ab00c1d >> > Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> > Tested: 100 unique boards, 25 SoC families, 36 builds out of 140 >> > >> > Boot Failures Detected: https://kernelci.org/boot/?v4.6.2-121-g6b5d7d0432d9&fail >> > >> > arm64: >> > >> > defconfig: >> > apm-mustang-kvm-guest: 1 failed lab >> > apm-mustang-kvm-uefi-guest: 1 failed lab >> > juno-kvm-guest: 1 failed lab >> > juno-kvm-uefi-guest: 1 failed lab >> >> All is well. >> >> These KVM failures are due to a QEMU upgrade, and are not related to the >> kernel. > > Are you also having trouble with the latest version of qemu ? > I wasn't the one looking into this, so I don't know the details. I think it was a broader issue with upgrading the rootfs, but not having a new enough QEMU. I'll look into it a little closer and let you knwo if it's a problem with the latest QEMU. Kevin
Powered by blists - more mailing lists