linux-kernel - Re: [PATCH] LinuxPPS (with new syscalls API)

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: <20070711152455.GK31193@csclub.uwaterloo.ca>
Date:	Wed, 11 Jul 2007 11:24:55 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	Rodolfo Giometti <giometti@...eenne.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	David Woodhouse <dwmw2@...radead.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] LinuxPPS (with new syscalls API) - new version

On Wed, Jul 11, 2007 at 03:18:46AM +0200, Roman Zippel wrote:
> This is really not an API that needs to deal with such large time range.

No one will want to use PPS API to keep accurate time past 2030?  Why
not?  Or should we be forced to invent a new PPS API before then to fix
this one?

Actually, come to think of it, is this passing a current time, or it it
passing an interval since last PPS?  If it is an interval, then yes
never mind, we don't need that many seconds (usually 1 or 2 at most).
For some reason I thought this was for passing the current time of a
stamp.

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