linux-kernel - Re: 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:	Thu, 28 Jan 2016 22:29:30 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Oleg Nesterov <oleg@...hat.com>, Andrey Wagin <avagin@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andy Lutomirski <luto@...capital.net>,
	Cyrill Gorcunov <gorcunov@...nvz.org>,
	"criu@...nvz.org" <criu@...nvz.org>, kvm@...r.kernel.org
Subject: Re: x86: Hardware breakpoints are not always triggered



On 28/01/2016 21:53, Oleg Nesterov wrote:
> > We use hardware breakpoints in CRIU and we found that sometimes we set
> > a break-point, but a process doesn't stop on it.
> 
> reproduced, and this certainly looks like kvm bug to me.

Yes, in all likelihood.  Thanks, I'll reproduce and look for a fix.

Paolo