From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by sourceware.org (Postfix) with ESMTP id DC636386183F for ; Mon, 18 Jan 2021 17:51:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DC636386183F Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-568-CtVtZxfCNTKyZAAEYeYHXw-1; Mon, 18 Jan 2021 12:51:08 -0500 X-MC-Unique: CtVtZxfCNTKyZAAEYeYHXw-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9A5EB107ACF5; Mon, 18 Jan 2021 17:51:07 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-112-110.ams2.redhat.com [10.36.112.110]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C0BC660861; Mon, 18 Jan 2021 17:51:06 +0000 (UTC) From: Florian Weimer To: "Dr. Todor Dimitrov" Cc: libc-help@sourceware.org Subject: Re: Glibc 2.31 - time64 with 64-bit kernel and 32-bit userland References: <5FDBA7C2-79E2-4B21-98EF-800694DEB500@technology.de> Date: Mon, 18 Jan 2021 18:51:01 +0100 In-Reply-To: <5FDBA7C2-79E2-4B21-98EF-800694DEB500@technology.de> (Todor Dimitrov's message of "Mon, 18 Jan 2021 18:43:01 +0100") Message-ID: <87mtx6m8vu.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-6.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2021 17:51:14 -0000 * Todor Dimitrov: > we=E2=80=99ve recently updated an `aarch64` system to Glibc 2.31 and we= =E2=80=99ve > 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 --=20 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'N= eill