From: "Arnd Bergmann" <arnd@arndb.de>
To: "Adhemerval Zanella Netto" <adhemerval.zanella@linaro.org>,
"Xi Ruoyao" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v5 2/3] linux: Fix ancillary 64-bit time timestamp conversion (BZ #28349, BZ#28350)
Date: Fri, 30 Sep 2022 16:56:33 +0200 [thread overview]
Message-ID: <2eb53654-6374-41e2-b84d-908cd5b8f9ee@app.fastmail.com> (raw)
In-Reply-To: <a7278b6a-326f-2ed9-9c14-a95219e18b75@linaro.org>
On Fri, Sep 30, 2022, at 3:46 PM, Adhemerval Zanella Netto via Libc-alpha wrote:
> On 30/09/22 10:09, Arnd Bergmann wrote:
>> On Fri, Sep 30, 2022, at 2:51 PM, Adhemerval Zanella Netto via Libc-alpha wrote:
>>> On 30/09/22 09:31, Szabolcs Nagy wrote:
>>>>>
>>>>> I used gcc 12.1.1, maybe it is a compiler issue?
>>>>
>>>> sorry it was my fault: old kernel headers.
>>>
>>> Right, but I am puzzled since it should not matter (at least glibc
>>> should handle it).
>>> What was miscompiled due wrong kernel header?
>>
>> Using SIOCGSTAMP/SIOCGSTAMPNS wtih 64-bit time_t requires kernel
>> headers after this 2019 commit:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0768e17073dc52
>
> But glibc does not use these definition internally or on tests.
My mistake. SO_TIMESTAMPNS was a different commit, this is the one
you need then:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=887feae36a
Arnd
next prev parent reply other threads:[~2022-09-30 14:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 20:15 [PATCH v5 0/3] Fix socket ancillary timestamp on 32 bit time_t ABIs Adhemerval Zanella
2022-01-27 20:15 ` [PATCH v5 1/3] support: Add support_socket_so_timestamp_time64 Adhemerval Zanella
2022-01-28 12:37 ` Florian Weimer
2022-01-27 20:15 ` [PATCH v5 2/3] linux: Fix ancillary 64-bit time timestamp conversion (BZ #28349, BZ#28350) Adhemerval Zanella
2022-01-28 13:22 ` Florian Weimer
2022-01-28 16:41 ` Adhemerval Zanella
2022-09-30 10:47 ` Szabolcs Nagy
2022-09-30 11:05 ` Szabolcs Nagy
2022-09-30 11:24 ` Adhemerval Zanella Netto
2022-09-30 12:31 ` Szabolcs Nagy
2022-09-30 12:51 ` Adhemerval Zanella Netto
2022-09-30 13:09 ` Arnd Bergmann
2022-09-30 13:46 ` Adhemerval Zanella Netto
2022-09-30 14:56 ` Arnd Bergmann [this message]
2022-09-30 15:33 ` Adhemerval Zanella Netto
2022-01-27 20:15 ` [PATCH v5 3/3] Linux: Only generate 64 bit timestamps for 64 bit time_t recvmsg/recvmmsg Adhemerval Zanella
2022-01-28 14:02 ` Florian Weimer
2022-01-28 16:42 ` 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=2eb53654-6374-41e2-b84d-908cd5b8f9ee@app.fastmail.com \
--to=arnd@arndb.de \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@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).