Re: [Y2038] [PATCH v3] scsi: bfa: Use ktime_get_real_seconds()

On Wed, Nov 11, 2015 at 1:22 AM, Arnd Bergmann wrote: > On Tuesday 10 November 2015 22:21:50 Amitoj Kaur Chawla wrote: >> On Tue, Nov 10, 2015 at 10:01 PM, Arnd Bergmann wrote: >> > On Tuesday 10 November 2015 19:27:49 Amitoj Kaur Chawla wrote: >> >> After looking

Re: [Y2038] [PATCH v3] scsi: bfa: Use ktime_get_real_seconds()

On Thursday 12 November 2015 14:12:52 Amitoj Kaur Chawla wrote: > On Wed, Nov 11, 2015 at 1:22 AM, Arnd Bergmann wrote: > > On Tuesday 10 November 2015 22:21:50 Amitoj Kaur Chawla wrote: > >> On Tue, Nov 10, 2015 at 10:01 PM, Arnd Bergmann wrote: > >> > You could

Re: [Y2038] [PATCH] drivers: md: use ktime_get_real_seconds()

On Wednesday 11 November 2015 19:23:33 Deepa Dinamani wrote: > get_seconds() API is not y2038 safe on 32 bit systems and the API > is deprecated. Replace it with calls to ktime_get_real_seconds() > API instead. Change mddev structure types to time64_t accordingly. > > 32 bit signed timestamps

Re: [Y2038] [PATCH] drivers: md: use ktime_get_real_seconds()

On Thu, Nov 12, 2015 at 1:56 PM, Arnd Bergmann wrote: > On Wednesday 11 November 2015 19:23:33 Deepa Dinamani wrote: > > get_seconds() API is not y2038 safe on 32 bit systems and the API > > is deprecated. Replace it with calls to ktime_get_real_seconds() > > API instead. Change

Re: [Y2038] [PATCH v3] scsi: bfa: Use ktime_get_real_seconds()

On Thursday 12 November 2015 17:52:51 Amitoj Kaur Chawla wrote: > On Thu, Nov 12, 2015 at 2:55 PM, Arnd Bergmann wrote: > > On Thursday 12 November 2015 14:12:52 Amitoj Kaur Chawla wrote: > >> I don't get a build error when I remove the time_t cast. Where am I going > >> wrong? >

[Y2038] [PATCH 1/2] scsi: bfa: Use ktime_get_real_seconds()

32 bit systems using 'struct timeval' will break in the year 2038, so we modify the code appropriately. This patch replaces the use of struct timeval and do_gettimeofday() with ktime_get_real_seconds() which returns a 64 bit value which is safer than struct timeval. This patch replaces u32 time

[Y2038] [PATCH] fs:affs:Replace time_t with time64_t

The affs code uses "time_t" and "get_seconds()". This will cause problems on 32-bit architectures in 2038 when time_t overflows. This patch replaces them with "time64_t" and "ktime_get_real_seconds()". This patch introduces expensive 64-bit divsion in "secs_to_datestamp()", considering this

[Y2038] [PATCH V1] serial:bfin-uart:Remove 'struct timeval'

The bfin-uart code uses real time with struct timeval. This will cause problems on 32-bit architectures in 2038 when time_t overflows. Since the code just needs delta value of time, it is not necessary to record them in real time. This patch changes the code to use the monotonic time instead,

Re: [Y2038] [PATCH V1] serial:bfin-uart:Remove 'struct timeval'

On Thursday 12 November 2015 21:45:47 DengChao wrote: > The bfin-uart code uses real time with struct timeval. This will > cause problems on 32-bit architectures in 2038 when time_t > overflows. > Since the code just needs delta value of time, it is not > necessary to record them in real time. >

Re: [Y2038] [PATCH v3] scsi: bfa: Use ktime_get_real_seconds()

On Thu, Nov 12, 2015 at 6:37 PM, Arnd Bergmann wrote: > On Thursday 12 November 2015 17:52:51 Amitoj Kaur Chawla wrote: >> On Thu, Nov 12, 2015 at 2:55 PM, Arnd Bergmann wrote: >> > On Thursday 12 November 2015 14:12:52 Amitoj Kaur Chawla wrote: >> >> I don't get a

[Y2038] [PATCH 0/2] fs:hpfs:Remove time_t

The hpfs code uses time_t which will overflow at 2038. If time_t is only internal used without being stored on disk, simply replacing it with time64_t is fine. Otherwise, since the range of time has been already lost when it is stored on disk, the only thing we can do is a cast between 32-bit

[Y2038] [PATCH 2/2] scsi: bfa: Remove use of 'time_t'

32 bit systems using 'time_t' will break in the year 2038, so we modify the code appropriately. This patch removes the cast to 'time_t' in the assignment statement since we are eventually removing the time_t definition from the kernel as an effort to solve the y2038 problem. This change impacts

Re: [Y2038] [PATCH] fs:affs:Replace time_t with time64_t

On Thursday 12 November 2015 21:40:41 DengChao wrote: > The affs code uses "time_t" and "get_seconds()". This will cause > problems on 32-bit architectures in 2038 when time_t overflows. > This patch replaces them with "time64_t" and > "ktime_get_real_seconds()". This patch introduces expensive

Re: [Y2038] [PATCH 2/2] fs:hpfs:Remove time_t used on disk

On Thursday 12 November 2015 21:26:03 DengChao wrote: > /* > + * Since time32_t is stored into media, the range has been already lost > + * for time64_t anyway. Only thing we can do is directly cast between > + * time32_t and time64_t. Forunately, time32_t won't overflow until 2106. > + */ > + >

[Y2038] y2038 tasks wanted

Hi Arnd, I'm looking for more y2038 tasks...please ;) How are you doling out y2038 tasks presently? (I'm not clear what's left undone, if any, from the outreachy queue) Thanks, Alison ___ Y2038 mailing list Y2038@lists.linaro.org