linux-kernel - RE: [PATCH] time: Provide full featured jiffies_to

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: <3908561D78D1C84285E8C5FCA982C28F3280B567@ORSMSX114.amr.corp.intel.com>
Date:	Fri, 16 May 2014 17:17:46 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Shy Shuky <rousya@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Steven Rostedt" <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	"Ingo Molnar" <mingo@...hat.com>,
	Mauro Chehab <m.chehab@...sung.com>,
	"xiexiuqi@...wei.com" <xiexiuqi@...wei.com>
Subject: RE: [PATCH] time: Provide full featured jiffies_to_nsecs() function

> How about get uptime by get_monotonic_boottime() directly, which's
> the same as /proc/uptime.

I don't know.  get_monotonic_boottime() had existed for many releases
at the point the uptime trace clock was added - so it was an available
choice. Maybe not noticed by

Is this function safe to call in every context (including NMI & machine check)?
[it uses read_seqcount_begin/read_seqcount_retry ... which I *think* is
safe ... but this stuff is tricky, so I'd like some reassurance].

Mauro, Steven: Did we just do math on jiffies because we wanted less overhead
in a tracepoint?

Bigger question (mostly for Mauro) ... what was the motivation for the "uptime"
tracer to begin with?  The rasdaemon code that is using it converts the times
from traces into absolute times (by adding an offset it computes by comparing
uptime and gettimeofday() when it starts).  But this would seem to be fraught
with problems:
1) Do we get this right for events that happen in daylight saving time shift windows?
2) Is there a "drift" problem for systems that stay up for months and rely on ntp
to keep wall clock time in line with reality?

-Tony