linux-kernel - Re: [PATCH] [RFC] Potential fix for leapsecond caused futex related load spikes

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: <20120703134134.GA19558@localhost.localdomain>
Date:	Tue, 3 Jul 2012 15:41:34 +0200
From:	Richard Cochran <richardcochran@...il.com>
To:	John Stultz <johnstul@...ibm.com>,
	Prarit Bhargava <prarit@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [RFC] Potential fix for leapsecond caused futex
 related load spikes

On Tue, Jul 03, 2012 at 02:05:36PM +0200, Sytse Wielinga wrote:
> On Tue, Jul 03, 2012 at 11:23:25AM +0200, Richard Cochran wrote:
> > I think the established practice of announcing the event by network is
> > the only sane way of handling this issue. The list of TAI-UTC offsets
> > belongs to what David Mills has called our "institutional memory", and
> > this is a user space issue. The kernel's job is to just live in the
> > moment and provide the right time for *now*.
> 
> I do suppose hardware clock and file system times will have to be UTC (or
> UTC-based local time) though?

Yes, you are right. Those things can never change. What I have in mind
is purely internal to the kernel and won't be visible in any way.

Thanks,
Richard

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