linux-kernel - Re: [PATCH] seqlock: serialize against writers

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:	Fri, 29 Aug 2008 12:29:42 -0400
From:	Gregory Haskins <ghaskins@...ell.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Gregory Haskins <gregory.haskins@...il.com>, mingo@...e.hu,
	rostedt@...dmis.org, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [PATCH] seqlock: serialize against writers

Andi Kleen wrote:
>> Im running it on a x86_64 box as we speak.  How can I tell if there is a
>> certain mode that is permitting this?
>>     
>
> If the boot up says you're running with PMtimer then it uses the fallback
> (usually happens on pre Fam10h AMD boxes). A typical Intel box
> would use the faster ring 3 only TSC path and then explode with your
> change I bet. 
>   

Thinking about this some more, perhaps the issue is I am not hitting the
contended path in vsyscall?

-Greg



Download attachment "signature.asc" of type "application/pgp-signature" (258 bytes)