Re: Glibc 2.31 - time64 with 64-bit kernel and 32-bit userland

["Dr. Todor Dimitrov" <dimitrov@technology.de>]

[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]

Yes:

uname -a
Linux  4.1.52 #1 SMP PREEMPT Mon Jan 4 13:54:08 CST 2021 aarch64 GNU/Linux

Unfortunately updating the kernel is not an option as it would require a new (not existing) BSP package. The only other option would be downgrading Glibc?

Thanks, Todor

> On 18. Jan 2021, at 18:51, Florian Weimer <fweimer@redhat.com> wrote:
> 
> * Todor Dimitrov:
> 
>> we’ve recently updated an `aarch64` system to Glibc 2.31 and we’ve
>> started seeing a lot of failing 403 and 407 syscalls. The kernel
>> version is 4.1.52 and the userland is 32-bit. Looking at the
>> implementation of `__clock_gettime64`, it seems that we are hitting
>> the following problem:
> 
> Are you sure this is an aarch64 system?
> 
>> `__NR_clock_gettime64` is defined for the 32-bit `arm` architecture
>> but not for `aarch64`. Is this a known issue? What would be the best
>> way to overcome it?
> 
> Upgrade your kernel to something that has 64-bit time_t support.
> 
> Thanks,
> Florian
> -- 
> Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
> 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3895 bytes --]