Re: [Y2038] [PATCH 13/16] hfs/hfsplus: use 64-bit inode timestamps

2019-11-13 Thread Viacheslav Dubeyko
> On Nov 13, 2019, at 11:06 AM, Arnd Bergmann wrote: > > On Wed, Nov 13, 2019 at 7:00 AM Viacheslav Dubeyko wrote: >>> On Nov 9, 2019, at 12:32 AM, Arnd Bergmann wrote: >>> * There are two time systems. Both are based on seconds since >>> * a particular time/date. >>> - * Unix: unsigned

Re: [Y2038] [PATCH 13/16] hfs/hfsplus: use 64-bit inode timestamps

2019-11-13 Thread Arnd Bergmann
On Wed, Nov 13, 2019 at 7:00 AM Viacheslav Dubeyko wrote: > > On Nov 9, 2019, at 12:32 AM, Arnd Bergmann wrote: > > * There are two time systems. Both are based on seconds since > > * a particular time/date. > > - * Unix: unsigned lil-endian since 00:00 GMT, Jan. 1, 1970 > > + * Unix:

Re: [Y2038] [PATCH 13/16] hfs/hfsplus: use 64-bit inode timestamps

2019-11-12 Thread Viacheslav Dubeyko
> On Nov 9, 2019, at 12:32 AM, Arnd Bergmann wrote: > > The interpretation of on-disk timestamps in HFS and HFS+ differs > between 32-bit and 64-bit kernels at the moment. Use 64-bit timestamps > consistently so apply the current 64-bit behavior everyhere. > > According to the official

Re: [Y2038] [PATCH 13/16] hfs/hfsplus: use 64-bit inode timestamps

2019-11-12 Thread Ernesto A . Fernández
On Fri, Nov 08, 2019 at 10:32:51PM +0100, Arnd Bergmann wrote: > The interpretation of on-disk timestamps in HFS and HFS+ differs > between 32-bit and 64-bit kernels at the moment. Use 64-bit timestamps > consistently so apply the current 64-bit behavior everyhere. > > According to the official