![[RTEMS Logo]](/images/logo.png){kind=logo}
Opened on 08/19/08 at 21:02:24
Last modified on 01/09/14 at 14:03:50
#1298 closed defect (fixed)
POSIX timer_settime incorrectly reject absolute timeouts in past.
| Reported by: | Tim FitzGeorge | Owned by: | Joel Sherrill |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.11 |
| Component: | score | Version: | 4.9 |
| Severity: | normal | Keywords: | |
| Cc: | gedare@…, cynt6007@… | Blocked By: | |
| Blocking: |
Description
The POSIX standard states that when timer_settime has timeout specified for a time that has already occurred, the expiration notification should be made immediately, and the call should succeed.
The RTEMS HEAD implementation has a specific test for this case (for TIMER_ABSTIME which incorrectly rejects the timeout with an error. This should be modified to conform to the standard.
Note that there is no test for a relative timeout in the past; this is passed straight to the watchdog routines. The 4.8 branch also lacks a check for both absolute and relative timers.
This bug report covers an issue first described on bug report 1296.
Attachments (1)
Change History (4)
Changed on 12/05/13 at 17:27:25 by Daniel Ramirez
| Attachment: | timer_settime.patch added |
|---|
comment:1 Changed on 01/08/14 at 04:36:39 by cynt6007
| Status: | new → assigned, cynt6007@vandals.uidaho.edu |
|---|
comment:2 Changed on 01/09/14 at 14:03:02 by Gedare Bloom
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed, gedare@rtems.org |
Patch committed. Close if OK, or request back-port if needed.
comment:3 Changed on 01/09/14 at 14:03:50 by Gedare Bloom
| Milestone: | 4.9 → 4.11 |
|---|
Patch to fix bug and update test cases