linux-kernel - Re: firewire: CLOCK_MONOTONIC

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]

Message-ID: <20140716123727.GA19379@twins.programming.kicks-ass.net>
Date:	Wed, 16 Jul 2014 14:37:27 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Clemens Ladisch <clemens@...isch.de>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org,
	linux1394-devel@...ts.sourceforge.net,
	John Stultz <john.stultz@...aro.org>
Subject: Re: firewire: CLOCK_MONOTONIC_RAW exposure

On Wed, Jul 16, 2014 at 01:34:21PM +0200, Clemens Ladisch wrote:
> Thomas Gleixner wrote:
> > I wonder why firewire exposed CLOCK_MONOTONIC_RAW to user space.
> >
> > What's the purpose of that? CLOCK_MONOTONIC_RAW is the raw time based
> > on the initial frequency setup of the clocksource. That can be quite
> > off from the NTP corrected frequency which is exposed by
> > CLOCK_MONOTONIC.
> 
> The purpose is to get a stable clock, i.e., to avoid clock rate changes
> caused by NTP corrections.

That's maybe half an answer; what do you need that for?

Content of type "application/pgp-signature" skipped