This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v9] y2038: Introduce the __ASSUME_TIME64_SYSCALLS define
On Fri, Aug 30, 2019 at 04:36:55PM +0000, Joseph Myers wrote:
> On Fri, 30 Aug 2019, Rich Felker wrote:
>
> > To clarify, none of the timespec ones "exactly match" -- the suffixed
> > syscalls on 32-bit require filling the padding around tv_nsec, whereas
>
> What do you mean by "require filling the padding"? I thought the
> conclusion in the kernel was that it dealt with zeroing the padding when
> reading a timespec64 from userspace on a 32-bit system (with the caveat of
> that not happening for compat tasks under 64-bit kernels before 5.1.5, and
> so the question in
> <https://sourceware.org/ml/libc-alpha/2019-05/msg00698.html> of whether to
> treat 5.1.0 through 5.1.4 as buggy and unsupported).
I wasn't aware of this change. Being that the unfortunate behavior
actually appeared in released kernel versions, I would lean towards
assuming userspace has to patch it up. I'm skeptical of just
considering these versions as "unusably buggy", since, at present and
until there are time64 binaries, they appear to work just fine. It
will only be at some point in the future when time64 userspace appears
that these kernel versions break things catastrophically.
Rich