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: <20070710160151.GB31195@csclub.uwaterloo.ca>
Date:	Tue, 10 Jul 2007 12:01:51 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Rodolfo Giometti <giometti@...eenne.com>
Cc:	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 Sun, Jul 01, 2007 at 09:24:41PM +0200, Rodolfo Giometti wrote:
>     struct pps_timedata_s {
>        __32 sec;
>        __32 nsec;
>     }
> 
> Ok? I think 32 bits are enought for keeping seconds... :)

You want to purposely define an API that will break in 23 years (or is
that 83 years since you made it unsigned potentially)?  Why not 64bit
for seconds and 32bit for nsec.  That should cover it for long enough.
When the unix time format was created 37 years ago, I could see thinking
32bit seemed reasonable, but why do it now.  We have ram enough for
64bits.

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