[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2u11+Ccoxk2hJpYTeyOVSOwZHyT6PZAE6_RSTMStN_pA@mail.gmail.com>
Date: Fri, 22 Jun 2018 16:19:35 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Viacheslav Dubeyko <slava@...eyko.com>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
y2038 Mailman List <y2038@...ts.linaro.org>,
Jeff Layton <jlayton@...hat.com>, Jan Kara <jack@...e.cz>,
Deepa Dinamani <deepa.kernel@...il.com>,
Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] hfs: stop using timespec based interfaces
On Wed, Jun 20, 2018 at 9:55 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Wed, Jun 20, 2018 at 6:55 PM, Viacheslav Dubeyko <slava@...eyko.com> wrote:
>> On Tue, 2018-06-19 at 21:42 +0200, Arnd Bergmann wrote:
>>> On Tue, Jun 19, 2018 at 7:03 PM, Viacheslav Dubeyko <slava@...eyko.com> wrote:
>>> /* time macros: convert between 1904-2040 and 1970-2106 range,
>>> * pre-1970 timestamps are interpreted as post-2038 times after
>>> wrap-around */
>>> -#define __hfsp_mt2ut(t) (be32_to_cpu(t) -
>>> 2082844800U)
>>> +#define __hfsp_mt2ut(t) ((time64_t)be32_to_cpu(t) -
>>> 2082844800U)
>>> #define __hfsp_ut2mt(t) (cpu_to_be32(t +
>>> 2082844800U))
>>>
>>> /* compatibility */
>>>
>>> I can submit that separately so that it can get backported into
>>> stable kernels if you like, with the type changes as a follow-up
>>> on top.
>>>
>>
>> Sounds good.
>
> Ok, I'll send an updated version with that patch first then.
I've now sent that patch with additional information that I got from reading the
XNU sources. Interestingly, that also uses the 1970-2106 time range that
I had in my original series, not the 1904-2040 time range that is documented.
Arnd
Powered by blists - more mailing lists