[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 Joel Sherrill):

 Replying to [comment:2 andrei.lupas]:
 > Indeed, behavior is according to POSIX spec, but in the "undefined" area
 > "The effect of destroying a semaphore upon which other threads are
 currently blocked is undefined."
 > In this case, the "undefined" behavior changed from SUCCESS to
 error:EBUSY, and this impacts some existing apps.

 Can you cite where you found that undefined behavior citation? I looked at
 the Change History section for the methods I thought this would be in and
 don't see it.

 Knowing when the behavior changed and being able to cite something would
 lend strength to providing a way to get the alternative behavior. I lean
 to it changing on a per semaphore instance basis rather than a single flag
 changing it for all.

 > On short term, I suppose I need to move to classic API semaphores.
 > Thanks a lot for the prompt feedback.

 No problem.
 > Andrei.

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