From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
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: Mon, 24 Jan 2022 13:13:25 +0100 [thread overview]
Message-ID: <87bl0149i2.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <372ae1ee-0163-7bf4-be1c-cc1f13b1a940@linaro.org> (Adhemerval Zanella's message of "Mon, 24 Jan 2022 09:07:09 -0300")
* Adhemerval Zanella:
>> typo: MSG_[C]TRUNC
>>
>> (I think this MSG_CTRUNC result is a remaining bug we need to fix
>> separately for time32 mode.)
>
> Do you mean not returning the MSG_CTRUNC?
No, if the caller uses CMSG_SPACE to allocate space for the expected
ancillary data, we should not produce MSG_CTRUNC by stuffing in
ancillary data that has not been requested. Maybe we can do this for
time32 code only. Again it seems that userspace emulation is rather
questionable here.
Thanks,
Florian
next prev parent reply other threads:[~2022-01-24 12:13 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 [this message]
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
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=87bl0149i2.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--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).