[RTEMS Project] #4844: Unchecked boundaries

[RTEMS trac]

#4844: Unchecked boundaries
---------------------------+------------------------------
 Reporter:  Daniel Páscoa  |       Owner:  Sebastian Huber
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  6.1
Component:  score          |     Version:  6
 Severity:  normal         |  Resolution:
 Keywords:  qualification  |  Blocked By:
 Blocking:                 |
---------------------------+------------------------------

Comment (by Daniel Páscoa):

 1 >>> We agree that changing the function prototype for
 rtems_message_queue_send,  rtems_message_queue_receive,
 _CORE_message_queue_Insert_message and other functions in-between could
 break existing applications and may not be acceptable to do so.
 So, one suggests dismissing this point of the ticket.

 2 >>> This point can be dismissed as it is now confirmed that necessary
 protections are already in place on the API entry point for
 _MRSP_Get_priority and _MRSP_Get_priority, which is the
 rtems_semaphore_set_priority (one can refer to the protections implemented
 by this function within code and/or ICD).

 3 >>> Yes, appending the _Assert( scheduler_index < _Scheduler_Count);
 just before the concerned line will solve it. Thanks

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