Date: Mon, 17 Oct 2022 15:11:39 -0400 From: Jan Schaumann <jschauma@netmeister.org> To: freebsd-hackers@freebsd.org Subject: Re: host unresponsive when setting time very far in the future Message-ID: <Y02o66HurMyn6NWK@netmeister.org> In-Reply-To: <CAOtMX2jiqy50oR3c_Z3O_=0-ZO8OC579M-qgQn2w6uKE3YVTzw@mail.gmail.com> References: <Y0y5cDu5aT/kLkuR@netmeister.org> <CADqw_gKvkhf6_N2UaZkxzcTau7Ewt%2BWBcx5=6aVmwC-BV_vbyA@mail.gmail.com> <Y01X%2B6cY2fdLzbqg@netmeister.org> <CANCZdfpduEOSZiYJboAHiuPZJvvieM3w68QY2QhxowcsEibxvA@mail.gmail.com> <Y02ZUcbiUVl7sJuK@netmeister.org> <CAOtMX2jiqy50oR3c_Z3O_=0-ZO8OC579M-qgQn2w6uKE3YVTzw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Alan Somers <asomers@freebsd.org> wrote: > On Mon, Oct 17, 2022 at 12:05 PM Jan Schaumann <jschauma@netmeister.org> wrote: > > Regardless of the root cause, though, I think > > something somewhere should return EINVAL before the > > system freaks out. :-) > Definitely. And the place that should do it is clock_ts_to_ct, where > the assertions were added in git rev 90a79ac5765 . They should be > converted from assertions into EINVALs. I've opened https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267157 for this. -Jan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Y02o66HurMyn6NWK>