[RTEMS Project] #3975: RTEMS 5 : sem_wait + sem_destroy behavior change

[RTEMS trac]

#3975: RTEMS 5 : sem_wait + sem_destroy behavior change
--------------------------+---------------------
 Reporter:  andrei.lupas  |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  admin         |     Version:  5
 Severity:  normal        |  Resolution:
 Keywords:                |  Blocked By:
 Blocking:                |
--------------------------+---------------------

Comment (by andrei.lupas):

 Replying to [comment:4 Sebastian Huber]:
 ...
 >
 > What we could do (since "The effect of destroying a semaphore upon which
 other threads are currently blocked is undefined.") is to flush the
 semaphore so that callers get woken up with EINVAL, we destroy the object
 and return EBUSY.

 Sounds good to me.
 Thanks.

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