From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4] linux: Fix ancillary 64-bit time timestamp conversion (BZ #28349, BZ #28350)
Date: Thu, 27 Jan 2022 10:55:34 -0300 [thread overview]
Message-ID: <80c7253b-8669-c692-ea58-625b3802a4d5@linaro.org> (raw)
In-Reply-To: <87tudpmhih.fsf@oldenburg.str.redhat.com>
On 27/01/2022 10:32, Florian Weimer wrote:
> * Adhemerval Zanella:
>
>>> Right, I expected something like that, which is why I insisted on adding
>>> the time64 symbol aliases.
>>
>> I can work on a patch for 2.35 if you think this is really required. Another
>> options would just to remove the MSG_CTRUNC fro 2.35.
>
> I really want that fix, but I think we can backport it just after the
> release.
Right, which fix exactly: the new time64 recvmsg/recvmmsg or not setting
MSG_CTRUNC is buffer is not large enough? Because the time64 recvmsg/recvmmsg
would require ABI additions and it should not be backportable.
next prev parent reply other threads:[~2022-01-27 13:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 18:52 Adhemerval Zanella
2022-01-12 13:36 ` Adhemerval Zanella
2022-01-21 13:53 ` Florian Weimer
2022-01-24 12:07 ` Adhemerval Zanella
2022-01-24 12:13 ` Florian Weimer
2022-01-24 12:23 ` Adhemerval Zanella
2022-01-24 12:38 ` Florian Weimer
2022-01-24 13:26 ` Adhemerval Zanella
2022-01-26 20:48 ` Florian Weimer
2022-01-27 11:23 ` Adhemerval Zanella
2022-01-27 11:58 ` Florian Weimer
2022-01-27 12:19 ` Adhemerval Zanella
2022-01-27 13:32 ` Florian Weimer
2022-01-27 13:55 ` Adhemerval Zanella [this message]
2022-01-27 14:09 ` Florian Weimer
2022-01-27 14:13 ` Adhemerval Zanella
2022-01-27 14:17 ` 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=80c7253b-8669-c692-ea58-625b3802a4d5@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--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).