linux-kernel - Re: [PATCH 4.4 00/37] 4.4.110-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]

Date:   Thu, 4 Jan 2018 20:50:55 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Thomas Voegtle <tv@...96.de>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, linux@...ck-us.net,
        shuahkh@....samsung.com, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review

On Thu, Jan 04, 2018 at 08:38:23PM +0100, Thomas Voegtle wrote:
> 
> When I start 4.4.110-rc1 on a virtual machine (qemu) init throws a
> segfault and the kernel panics (attempted to kill init).
> The VM host is a Haswell system.
> 
> The same kernel binary boots fine on a (other) Haswell system.
> 
> I tried:
> 
> 4.4.110-rc1     broken
> 4.4.109         ok
> 4.9.75-rc1      ok

Does 4.15-rc6 also work ok?

> All systems are OpenSuSE 42.3 64bit.
> 
> qemu is started only with:
> qemu-system-x86_64 -m 2048 -enable-kvm  -drive
> file=tvsuse,format=raw,if=none,id=virtdisk0 -device
> virtio-blk-pci,scsi=off,drive=virtdisk0
> 
> Am I the only one who sees this? Has anyone booted that kernel on qemu?

Any chance we can see the panic?

There's another error report of this same type of thing on this thread,
did you see that?

thanks,

greg k-h