public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug nptl/17504] New: mq_timedreceive and mq_timedsend do not use a monotonic clock
@ 2014-10-23 9:53 Dean_Jenkins at mentor dot com
2015-08-27 22:12 ` [Bug librt/17504] " jsm28 at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: Dean_Jenkins at mentor dot com @ 2014-10-23 9:53 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=17504
Bug ID: 17504
Summary: mq_timedreceive and mq_timedsend do not use a
monotonic clock
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nptl
Assignee: unassigned at sourceware dot org
Reporter: Dean_Jenkins at mentor dot com
CC: drepper.fsp at gmail dot com
In an embedded ARM project the system clock aka CLOCK_REALTIME starts at the
1970 EPOCH when the system is booted. mq_timedreceive() and mq_timedsend()
appear to use the CLOCK_REALTIME which I think is a POSIX requirement.
Unfortunately, in our project there is no RTC chip and the system clock is
updated by a GPS based timebase to the present time and date on each boot-up.
This can cause mq_timedreceive() and mq_timedsend() to misbehave because the
timespec used is for an absolute time which is still in 1970.
I see many discussions on the Internet about this clock limitation and
operating systems such as QNX have resolved the issue by implementing monotonic
variants of mq_timedreceive() and mq_timedsend(). Would something similar be
possible for Linux glibc ?
Are there any workarounds to this clock limitation because my Internet searches
have not found any ?
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug librt/17504] mq_timedreceive and mq_timedsend do not use a monotonic clock
2014-10-23 9:53 [Bug nptl/17504] New: mq_timedreceive and mq_timedsend do not use a monotonic clock Dean_Jenkins at mentor dot com
@ 2015-08-27 22:12 ` jsm28 at gcc dot gnu.org
0 siblings, 0 replies; 2+ messages in thread
From: jsm28 at gcc dot gnu.org @ 2015-08-27 22:12 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=17504
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|nptl |librt
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-08-27 22:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-10-23 9:53 [Bug nptl/17504] New: mq_timedreceive and mq_timedsend do not use a monotonic clock Dean_Jenkins at mentor dot com
2015-08-27 22:12 ` [Bug librt/17504] " jsm28 at gcc dot gnu.org
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).