From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Stafford Horne <shorne@gmail.com>,
GLIBC patches <libc-alpha@sourceware.org>
Subject: Re: [PATCH] timex: Use 64-bit fields on 32-bit TIMESIZE=64 systems
Date: Mon, 18 Oct 2021 17:01:10 -0300 [thread overview]
Message-ID: <d40500bc-8219-6c82-a11f-790607ede687@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110181933560.114463@digraph.polyomino.org.uk>
On 18/10/2021 16:35, Joseph Myers wrote:
> On Mon, 18 Oct 2021, Adhemerval Zanella via Libc-alpha wrote:
>
>> So master is broken on riscv32 (both misc/tst-ntp_gettime and
>> misc/tst-ntp_gettimex aborts) and I guess it is on arc as well.
>>
>> 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.
>>
>> The patch looks ok and we will need to backport it as well.
>
> If it's broken for existing architectures in a release, there should be a
> bug filed in Bugzilla if not already present, then marked RESOLVED/FIXED
> with target milestone set to 2.35 once the fix is pushed so that the fix
> appears in the generated list of fixed bugs in NEWS.
>
I created https://sourceware.org/bugzilla/show_bug.cgi?id=28469
prev parent reply other threads:[~2021-10-18 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 21:17 Stafford Horne
2021-10-18 17:29 ` Adhemerval Zanella
2021-10-18 18:55 ` Adhemerval Zanella
2021-10-18 19:35 ` Joseph Myers
2021-10-18 20:01 ` Adhemerval Zanella [this message]
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=d40500bc-8219-6c82-a11f-790607ede687@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=shorne@gmail.com \
/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).