[RTEMS Project] #2692: User extensions execution order must be clarified

[RTEMS trac]

#2692: User extensions execution order must be clarified
-----------------------------+------------------------------
 Reporter:  sebastian.huber  |       Owner:  sebastian.huber
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:  4.12
Component:  cpukit           |     Version:  4.11
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+------------------------------

Comment (by Sebastian Huber <sebastian.huber@…>):

 In [changeset:"709f38a97287ff1aa8e8c0668c2d066e711db87c/rtems"]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="709f38a97287ff1aa8e8c0668c2d066e711db87c"
 score: Use chain iterator for user extensions

 Add a lock and use a chain iterator for safe iteration during concurrent
 user extension addition and removal.

 Ensure that dynamically added thread delete and fatal extensions are
 called in reverse order.

 Update #2555.
 Update #2692.
 }}}

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