From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4EE1A3858404; Mon, 18 Oct 2021 20:00:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4EE1A3858404 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug time/28469] New: linux: struct timex is not correctly set for 32-bit systems with TIMESIZE=64 Date: Mon, 18 Oct 2021 20:00:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: time X-Bugzilla-Version: 2.34 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2021 20:00:53 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28469 Bug ID: 28469 Summary: linux: struct timex is not correctly set for 32-bit systems with TIMESIZE=3D64 Product: glibc Version: 2.34 Status: NEW Severity: normal Priority: P2 Component: time Assignee: unassigned at sourceware dot org Reporter: adhemerval.zanella at linaro dot org Target Milestone: --- On riscv32 there are two regressions: FAIL: misc/tst-ntp_gettime FAIL: misc/tst-ntp_gettimex On Linux side, the clock_adjtime syscall (kernel/time/posix-timers.c:1112) which maps to __NR_clock_gettime64 on 32-bit with legacy 32-bit and __NR_clock_gettime otherwise always use __kernel_timex. Since 32-bit systems with TIMESIZE=3D64 __USE_TIME_BITS64 is not defined, o= n suc systems the wrong kernel interface is used. --=20 You are receiving this mail because: You are on the CC list for the bug.=