linux-kernel - Re: Duplicate vsyscall/vdso gettimeofday implementations on x86

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, 17 Jul 2009 15:54:44 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...x.de>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Duplicate vsyscall/vdso gettimeofday implementations on x86_64

On Sat, 2009-07-18 at 00:12 +0200, Andi Kleen wrote:
> john stultz <johnstul@...ibm.com> writes:
> 
> > I think the implementation in vclock_gettime.c is nice, as it mostly
> > reuses the clock_gettime() code, but I don't think it actually gets
> > called.
> 
> It depends on what glibc uses.

Hrmm. Can we deprecate the old method and push glibc to use the new one?
If we remove it the vsyscall interface will old glibc's fall-back
gracefully? 

thanks
-john


--
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/