[RTEMS Project] #4338: rtems_clock_set(): Cannot set future dates later than approximately 2105

[RTEMS trac]

#4338: rtems_clock_set(): Cannot set future dates later than approximately 2105
-------------------------------------------------+-------------------------
 Reporter:  Frank Kuehndel                       |       Owner:  Sebastian
                                                 |  Huber
     Type:  defect                               |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.1
Component:  rtems                                |     Version:  6
 Severity:  normal                               |  Resolution:
 Keywords:  rtems_clock_set, 2514,               |  Blocked By:
  _TOD_To_seconds                                |
 Blocking:                                       |
-------------------------------------------------+-------------------------

Comment (by Joel Sherrill):

 Will switching to time_t instead of uint32_t largely resolve this?

 I think you might have missed some Classic API methods which might
 overflow. I think anything using uint32_t or rtems_interval related to
 seconds or ticks over long intervals is suspect. I spotted these:

 * rtems_clock_get_seconds_since_epoch() uses rtems_interval.
 * rtems_clock_get_ticks_since_boot() also uses rtems_interval but I think
 this overflows sooner than we'd like


 I think the Classic API time of day structure is OK.

--
Ticket URL: <http://devel.rtems.org/ticket/4338#comment:1>
RTEMS Project <http://www.rtems.org/>
RTEMS Project