#4211: _Timespec_To_ticks overflow
-------------------------+---------------------
Reporter: Chris Johns | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone: 6.1
Component: score | Version: 6
Severity: normal | Resolution:
Keywords: | Blocked By:
Blocking: |
-------------------------+---------------------
Comment (by Chris Johns):
Replying to [comment:5 Sebastian Huber]:
> I think the general question is what should be the behaviour if a user
specifies a timeout which is after the specified uptime of the system
(which is WATCHDOG_MAX_SECONDS, about 544 years). See also
_Watchdog_Is_far_future_timespec().
Yes that would work. If the `tv_sec` field is more than
`WATCHDOG_MAX_SECONDS` limit it to that value. We need to make the
conversion predictable for all possible `timespec` input values.
--
Ticket URL: <http://devel.rtems.org/ticket/4211#comment:6>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs
