On 12/17/19 6:11 PM, Sean Christopherson wrote:
On Wed, Nov 27, 2019 at 07:24:09AM -0800, Sean Christopherson wrote:
On Wed, Nov 20, 2019 at 11:28:43AM -0800, Sean Christopherson wrote:
On Wed, Nov 20, 2019 at 02:04:38PM -0500, Derek Yerger wrote:
Debug patch attached. Hopefully it finds something, it took me an
embarassing number of attempts to get correct, I kept screwing up checking
a bit number versus checking a bit mask...
<0001-thread_info-Add-a-debug-hook-to-detect-FPU-changes-w.patch>
Should this still be tested despite Wanpeng Li’s comments that the issue may
have been fixed in a 5.3 release candidate?
Yes.
The actual bug fix, commit e751732486eb3 (KVM: X86: Fix fpu state crash in
kvm guest), is present in v5.2.7.
Unless there's a subtlety I'm missing, commit d9a710e5fc4941 (KVM: X86:
Dynamically allocate user_fpu) is purely an optimization and should not
have a functional impact.
Any update on this? Syzkaller also appears to be hitting this[*], but it
hasn't been able to generate a reproducer.
[*] https://syzkaller.appspot.com/bug?extid=00be5da1d75f1cc95f6b
Still working on it. Not sure why but now my initrd images have quadrupled in
size with the latest kernel, so I'm at an impasse and stuck at 5.2 until I can
size up my /boot
Will try to fix this week.
