On Sun, Oct 16, 2022 at 10:28:41PM +, RVP wrote:
> > and how we ended up picking this particular value?
> >
>
> Punting to nia@...
I'm 99% positive it was trial and error.
David Brownlee wrote:
> > RVP wrote:
> > > There is a check in the kernel. In sys/kern/kern_time.c:
> > >
> > > 190 /*
> > > 191 * The time being set to an unreasonable value will cause
> > > 192 * unreasonable system behaviour.
> > > 193 */
>
On Sun, 16 Oct 2022, Jan Schaumann wrote:
Do we have examples of what this "unreasonable system
behaviour" might be,
From the commit message[1]:
---
kern_time: prevent the system clock from being set too low or high
currently doing this will drive KUBSAN haywire and possibly cause
system
In article ,
Jan Schaumann wrote:
>-=-=-=-=-=-
>
>RVP wrote:
>
>> There is a check in the kernel. In sys/kern/kern_time.c:
>>
>> 190 /*
>> 191 * The time being set to an unreasonable value will cause
>> 192 * unreasonable system behaviour.
>> 193
RVP wrote:
> There is a check in the kernel. In sys/kern/kern_time.c:
>
> 190 /*
> 191 * The time being set to an unreasonable value will cause
> 192 * unreasonable system behaviour.
> 193 */
> 194 if (ts->tv_sec < 0 || ts->tv_sec >
On Sun, 16 Oct 2022 at 15:34, Jan Schaumann wrote:
>
> RVP wrote:
> > On Sat, 15 Oct 2022, Jan Schaumann wrote:
> >
> > > - I just can't _set_ the clock to any value above
> > > 68719476736. Anybody know why?
> > >
> >
> > There is a check in the kernel. In sys/kern/kern_time.c:
> >
> > 190
RVP wrote:
> On Sat, 15 Oct 2022, Jan Schaumann wrote:
>
> > - I just can't _set_ the clock to any value above
> > 68719476736. Anybody know why?
> >
>
> There is a check in the kernel. In sys/kern/kern_time.c:
>
> 190 /*
> 191 * The time being set to an unreasonable
On Sat, 15 Oct 2022, Jan Schaumann wrote:
- I just can't _set_ the clock to any value above
68719476736. Anybody know why?
There is a check in the kernel. In sys/kern/kern_time.c:
190 /*
191 * The time being set to an unreasonable value will cause
192 *
Hey,
I just noticed that I'm unable to set my system clock
to date beyond 4147-08-20T07:32:16:
# date 414708200732.16; date +%s
Sun Aug 20 07:32:16 UTC 4147
68719476736
# date 414708200732.17
date: settimeofday: Invalid argument
With a tv_sec value of 68719476737 well below any max
for the
