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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 29 Nov 2017 14:45:21 -0800
From:   Andi Kleen <>
To:     Paolo Bonzini <>
Cc:     Wanpeng Li <>,,,
        Radim Krčmář <>,
        Wanpeng Li <>,
        Jim Mattson <>
Subject: Re: [PATCH] KVM: VMX: Cache IA32_DEBUGCTL in memory

On Wed, Nov 29, 2017 at 11:26:30PM +0100, Paolo Bonzini wrote:
> On 29/11/2017 19:20, Andi Kleen wrote:
> > But I haven't looked too closely, but I suspect you'll clobber global
> > kernel debugger state this way.
> I checked all callers of update_debugctlmsr, and couldn't find any that
> could run asynchronously while KVM is caching the value.  For example
> __switch_to_xtra would always run before the sched_in notifier.

True. It would only be a problem if the debugger supported branch stepping
or LBRs, which it doesn't seem to currently.


Powered by blists - more mailing lists