Messages in this thread | | | Subject | Re: [PATCH 01/12] Ext4: Fix extended timestamp encoding and decoding | From | Elmar Stellnberger <> | Date | Mon, 30 Nov 2015 15:46:06 +0100 |
| |
On 30.11.2015 15:16, Theodore Ts'o wrote: > On Sun, Nov 29, 2015 at 10:30:39PM +0100, Arnd Bergmann wrote: >> The other large missing piece is the system call implementation. I have >> posted a series earlier this year before my parental leave, and it's >> currently lacking review from libc folks, and blocked on me to update >> the series and post it again. > > I assume that this also means there hasn't been much thought about > userspace support above libc? i.e., how to take a 64-bit time64_t (or > changing the size of time_t) and translating that to a string using > some kind of version of ctime() and asctime(), and how to parse a > post-2038 date string and turning it into a 64-bit time_t on a 32-bit > platform? >
Arnd, I would just like to tell you how much I welcome your decision for a new __kernel_time64_t! As a time[64]_t is basically well defined counting artificial seconds since the epoch (1970-01-01 00:00) where every year divisible by four is a leap year that is for the meanwhile already sufficient to make use of your new type. I just think about the Mayan calendar application which I have implemented last year (Though I have not brought it to a publishable state yet). A single typedef should be sufficient to let it make use of time64_t (it directly uses this type as well as long long internally for its calculations rather than the glibc time format functions).
| |