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

Date:	Wed, 16 Jul 2014 11:57:10 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	John Stultz <john.stultz@...aro.org>
Subject: firewire: CLOCK_MONOTONIC_RAW exposure

Stefan,

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.

If there is no real good reason, I'd really like to remove that.

Thanks,

	tglx

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