linux-kernel - Re: [CRIU] x86: Hardware breakpoints are not always triggered

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:	Sun, 31 Jan 2016 12:01:53 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Andrew Vagin <avagin@...tuozzo.com>,
	Andrey Wagin <avagin@...il.com>
Cc:	kvm@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"criu@...nvz.org" <criu@...nvz.org>,
	Cyrill Gorcunov <gorcunov@...nvz.org>
Subject: Re: [CRIU] x86: Hardware breakpoints are not always triggered



On 29/01/2016 23:21, Andrew Vagin wrote:
> On Thu, Jan 28, 2016 at 02:42:25PM -0800, Andrey Wagin wrote:
>> On Thu, Jan 28, 2016 at 10:33:28PM +0100, Paolo Bonzini wrote:
>>>
>>>
>>> On 28/01/2016 09:31, Andrey Wagin wrote:
>>>> I tried to print drX registers after a break-point. Looks like they
>>>> are set correctly.
>>>
>>> Can you try this KVM patch?
>>
>> Looks like it fixes a case when reproducers are running only in VM.
> 
> Actually Oleg's reproducer detects the bug with this patch when they are
> rinning only in VM.

That's actually a good thing, because the patch was a long shot and I
had no clue _why_ it would have fixed the bug.  Oleg's reproducer
spanning host and a VM actually gives me an idea of what is going on,
I'll try to reproduce this week.

Paolo