linux-kernel - Re: [PATCH] Close small window for vsyscall time inconsistencies

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 07 Apr 2008 13:29:44 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Roman Zippel <zippel@...ux-m68k.org>,
	john stultz <johnstul@...ibm.com>,
	Paul Mackerras <paulus@...ba.org>,
	Tony Luck <tony.luck@...el.com>, Ingo Molnar <mingo@...e.hu>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Close small window for vsyscall time inconsistencies

Thomas Gleixner <tglx@...utronix.de> writes:
>  
>> So instead of shooting in the dark, I'd suggest to collect some
>>  numbers first,
>
> That's what we did and John's analysis of the problem is pretty
> correct.

The source of the problem is that RDTSC is not always 100% sync
right?

We debugged a similar problem a long time ago and in that case
it was the CPU speculating around the RDTSC. That was stopped
by adding the CPUIDs to sync the core.

I would double check that the CPUIDs are still executed as needed
on the systems showing the issue.

(the code to turn that on and off is somewhat subtle and breaks occasionally)

Also it was assumed at some point it wasn't needed on P4, but that turned
out to be wrong later. Perhaps the enable logic is still not quite
right.

Or perhaps the CPUIDs need to be moved inside or outside the 
seqlocks?

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/