From: Sundeep KOKKONDA <sundeep.kokkonda@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Suspected bug in mq_timedreceive
Date: Thu, 30 Jun 2022 19:13:17 +0530 [thread overview]
Message-ID: <CAG+0KzPONMRAvBQjHMfcx3kr-tm-LBpq=rr56TxonZyi_BiPag@mail.gmail.com> (raw)
In-Reply-To: <B9269CF4-A651-4AAF-8BFC-19D902C3F321@linaro.org>
Hello,
When will be the 2.36 release? I've to backport the patch to my project.
Will you implement the patch or can I send?
Thanks,
Sundeep K.
On Thu, 30 Jun, 2022, 16:49 Adhemerval Zanella, <
adhemerval.zanella@linaro.org> wrote:
>
>
> > On 30 Jun 2022, at 08:10, Adhemerval Zanella <
> adhemerval.zanella@linaro.org> wrote:
> >
> >
> >
> >> On 30 Jun 2022, at 03:37, sundeep.kokkonda--- via Libc-help <
> libc-help@sourceware.org> wrote:
> >>
> >> That test would be correct if mq_timedreceive returned 0 on success, as
> is
> >> the case for mq_timedsend. However, mq_timedreceive actually returns the
> >> number of bytes read, so the correct test is:
> >>
> >>
> >>
> >> If (ret >= 0 || errno != ENOSYS)
> >>
> >> return ret;
> >
> > Yeah, this is incorrect. I will open a bug an fix it on all affected
> releases.
> > At least for 2.36 the time64 code path is only used if the target date
> can not
> > be fit in 32-bit time_t.
>
> I have opened https://sourceware.org/bugzilla/show_bug.cgi?id=29304
next prev parent reply other threads:[~2022-06-30 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 6:37 sundeep.kokkonda
2022-06-30 11:10 ` Adhemerval Zanella
2022-06-30 11:19 ` Adhemerval Zanella
2022-06-30 13:43 ` Sundeep KOKKONDA [this message]
2022-06-30 14:15 ` 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='CAG+0KzPONMRAvBQjHMfcx3kr-tm-LBpq=rr56TxonZyi_BiPag@mail.gmail.com' \
--to=sundeep.kokkonda@gmail.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).