lkml.org 
[lkml]   [2015]   [Oct]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [RESEND PATCH] timerfd: Allow TFD_TIMER_CANCEL_ON_SET with relative timeouts
Date
On Monday 19 October 2015 11:53:25 John Stultz wrote:
>
> But yea. At the same time I get you want to avoid user-pain like in
> the case of the badly initialized RTC, but in that case would
> returning 0 for RTC reads greater then y2038 on 32 bit systems be a
> more sane fix?

I like that idea. In theory we could go further and check that the RTC
is somewhere between 2015 and 2037 (or higher on 64-bit systems) but
return 0 (1970) for anything that is outside of that range. That might
have side-effects for users that have a legitimate reason to backdate
their clocks though.

Arnd


\
 
 \ /
  Last update: 2015-10-20 10:41    [W:0.071 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site