Re: [RFC 06/32] isofs: fix timestamps beyond 2027

2014-05-31 Thread H. Peter Anvin
On 05/31/2014 12:59 AM, Geert Uytterhoeven wrote: > On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote: >> isofs uses a 'char' variable to load the number of years since >> 1900 for an inode timestamp. On architectures that use a signed >> char type by default, this results in an invalid date f

Re: [RFC 06/32] isofs: fix timestamps beyond 2027

2014-05-31 Thread Geert Uytterhoeven
On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote: > isofs uses a 'char' variable to load the number of years since > 1900 for an inode timestamp. On architectures that use a signed > char type by default, this results in an invalid date for > anything beyond 2027. > > This adds a cast to 'u8'

[RFC 06/32] isofs: fix timestamps beyond 2027

2014-05-30 Thread Arnd Bergmann
isofs uses a 'char' variable to load the number of years since 1900 for an inode timestamp. On architectures that use a signed char type by default, this results in an invalid date for anything beyond 2027. This adds a cast to 'u8' for the year number, which should extend the shelf life of the fil