This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v2 2/7] y2038: Introduce __ASSUME_64BIT_TIME define
- From: Stepan Golosunov <stepan at golosunov dot pp dot ru>
- To: Lukasz Majewski <lukma at denx dot de>
- Cc: Joseph Myers <joseph at codesourcery dot com>, libc-alpha at sourceware dot org, Arnd Bergmann <arnd at arndb dot de>, Paul Eggert <eggert at cs dot ucla dot edu>
- Date: Fri, 31 May 2019 15:37:53 +0400
- Subject: Re: [PATCH v2 2/7] y2038: Introduce __ASSUME_64BIT_TIME define
- References: <20190414220841.20243-1-lukma@denx.de> <20190429104613.16209-1-lukma@denx.de> <20190429104613.16209-3-lukma@denx.de> <alpine.DEB.2.21.1904292138430.21580@digraph.polyomino.org.uk> <20190430110505.2a0c7d1a@jawa> <alpine.DEB.2.21.1905021431060.4027@digraph.polyomino.org.uk> <20190506165510.7a6c20d1@jawa> <alpine.DEB.2.21.1905071523000.3445@digraph.polyomino.org.uk> <20190508121840.39aaedcb@jawa>
08.05.2019 в 12:18:40 +0200 Lukasz Majewski написал:
> Hi Joseph,
>
> > On Mon, 6 May 2019, Lukasz Majewski wrote:
> >
> > > > So, which is (or will be) the case in 5.1 release? Padding
> > > > ignored or not?
> > >
> > > As confirmed in the other mail - the padding is ignored in Linux
> > > kernel (and the fix patch for x32 is up its way to be pulled).
> >
> > Did the patch to ignore padding (for compat syscalls under 64-bit
> > kernels, non-x32) make it into the final 5.1 release?
>
> As fair as I can tell, it was not pulled to 5.1.
The patch went into 5.1.5 and 5.2-rc1.
So the question now is:
Should Linux 5.1.0–5.1.4 be considered buggy and unsupported, or
should glibc clear padding around tv_nsec on 32-bit architectures when
__LINUX_KERNEL_VERSION < 0x050105 and 64-bit kernel exists?