linux-kernel - Re: [PATCH v5 0/8] vDSO time changes for 2.6.40

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] [day] [month] [year] [list]

Message-ID: <BANLkTikHTLGnbY++=MmAwEoi8yLiNAdemA@mail.gmail.com>
Date:	Mon, 23 May 2011 11:28:07 -0400
From:	Andrew Lutomirski <luto@....edu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	x86@...nel.org, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <eric.dumazet@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Borislav Petkov <bp@...64.org>
Subject: Re: [PATCH v5 0/8] vDSO time changes for 2.6.40

On Mon, May 23, 2011 at 11:23 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Mon, May 23, 2011 at 6:31 AM, Andy Lutomirski <luto@....edu> wrote:
>> [Patch 8/8 is brand-new and optional.  If anyone objects to it,
>>  please just drop it for 2.6.40 and I'll fix it for 2.6.41.]
>
> Hmm. I would just put it into 7/8 immediately, and never have the
> stupid read-lock loop in the first place.
>
> Or I would just say "the time() system call just isn't that critical,
> let's not even bother".

I have no particular preference.  The only argument I can make is that
the change deletes code and it lets us tell the glibc people "not only
can you stop using a silly old interface but you can make your code
0.4ns faster."

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