[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170426104331.nxfk5gopskaklpmj@crack.deadbeast.net>
Date: Wed, 26 Apr 2017 06:43:33 -0400
From: "G. Branden Robinson" <g.branden.robinson@...il.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Cc: "Dmitry V. Levin" <ldv@...linux.org>,
David Howells <dhowells@...hat.com>,
Jeff Layton <jlayton@...hat.com>,
lkml <linux-kernel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
linux-man <linux-man@...r.kernel.org>
Subject: Re: Revised statx(2) man page for review
At 2017-04-26T07:42:12+0200, Michael Kerrisk (man-pages) wrote:
> On 04/25/2017 10:06 PM, Dmitry V. Levin wrote:
> > On Tue, Apr 25, 2017 at 01:14:26PM +0200, Michael Kerrisk (man-pages) wrote:
> > [...]
> >> The file timestamps are structures of the following type:
> >>
> >> struct statx_timestamp {
> >> __s64 tv_sec; /* Seconds since the Epoch (UNIX time) */
> >> __s32 tv_nsec; /* Nanoseconds before or since tv_sec */
> >> };
> >
> > Nanoseconds since tv_sec. The "before tv_sec" is not implemented yet
> > and I hope nobody is going to implement it for the reasons I mentioned
> > in https://marc.info/?i=20170422192743.GA17005%40altlinux.org
>
> Thanks Dmitry. Fixed.
If you give a programmer a signed type, he or she will cheerfully stuff
negative values into it, perhaps to carry out-of-band information as
with IEEE NaNs and tagged pointers.
The user should be admonished against using the full range of the type
in any case ([0, 1e9 - 1]).
Regards,
Branden
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists