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, 10 Jan 2019 15:00:11 -0500 (EST)
From:   Vince Weaver <>
To:     Peter Zijlstra <>
cc:, Ingo Molnar <>,
        Arnaldo Carvalho de Melo <>
Subject: Re: perf: rdpmc bug when viewing all procs on remote cpu

On Thu, 10 Jan 2019, Vince Weaver wrote:

> On Thu, 10 Jan 2019, Vince Weaver wrote:
> > However if you create an all-process attached to CPU event:
> > 	perf_event_open(attr, -1, X, -1, 0);
> > the mmap event index is set as if this were a valid event and so the rdpmc
> > succeeds even though it shouldn't (we're trying to read an event value
> > on a remote cpu with a local rdpmc).
> For a test case, try the
> 	tests/rdpmc/rdpmc_attach_other_cpu
> test found in my perf_event_tests suite
> 	git clone

and that was a cut-and-paste error, I meant
and I was wrong, it does affect AMD machines too.


Powered by blists - more mailing lists