From: Florian Weimer <fweimer@redhat.com>
To: "Dr. Todor Dimitrov" <dimitrov@technology.de>
Cc: libc-help@sourceware.org
Subject: Re: Glibc 2.31 - time64 with 64-bit kernel and 32-bit userland
Date: Mon, 18 Jan 2021 18:51:01 +0100 [thread overview]
Message-ID: <87mtx6m8vu.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <5FDBA7C2-79E2-4B21-98EF-800694DEB500@technology.de> (Todor Dimitrov's message of "Mon, 18 Jan 2021 18:43:01 +0100")
* 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
next prev parent reply other threads:[~2021-01-18 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 17:43 Dr. Todor Dimitrov
2021-01-18 17:51 ` Florian Weimer [this message]
2021-01-18 17:57 ` Dr. Todor Dimitrov
2021-01-18 19:31 ` Adhemerval Zanella
2021-01-18 20:10 ` Dr. Todor Dimitrov
2021-01-18 20:14 ` Florian Weimer
2021-01-18 20:31 ` Adhemerval Zanella
2021-01-18 20:35 ` Florian Weimer
2021-01-18 21:22 ` Adhemerval Zanella
2021-01-19 11:23 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtx6m8vu.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=dimitrov@technology.de \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).