linux-kernel - Re: [PATCH 0/4] KVM: nVMX: prepare

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: <CANRm+CyNB9=X9wpACG4KtUiO1Mp-0JUWuXvbkXPEN7V69hjrEA@mail.gmail.com>
Date:   Thu, 28 Dec 2017 16:39:48 +0800
From:   Wanpeng Li <kernellwp@...il.com>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     linux-kernel@...r.kernel.org, kvm <kvm@...r.kernel.org>
Subject: Re: [PATCH 0/4] KVM: nVMX: prepare_vmcs02 optimizations

2017-12-27 22:28 GMT+08:00 Paolo Bonzini <pbonzini@...hat.com>:
> On 25/12/2017 11:08, Wanpeng Li wrote:
>>> I observe L1(latest kvm/queue) panic and L0(latest kvm/queue)
>>> calltrace, I'm not sure whether it is caused by this patchset.
>> It can be reproduced steadily by running kvm-unit-tests in L1.
>
> It works here, can you show the L0 call trace and/or bisect it?

L0 call trace has already been posted here.
https://lkml.org/lkml/2017/12/25/53 In addition, the splatting is
still there after I revert the last 9 nVMX optimization patches in
kvm/queue. So it is not caused by this patchset. :)

Regards,
Wanpeng Li