[RTEMS Project] #2725: Classic binary semaphores without a locking protocol can be released by everyone

[RTEMS trac]

#2725: Classic binary semaphores without a locking protocol can be released by
everyone
-----------------------------+------------------------------
 Reporter:  sebastian.huber  |       Owner:  sebastian.huber
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:  4.12
Component:  cpukit           |     Version:  4.10
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+------------------------------
Description changed by chrisj:

Old description:

> The Classic binary semaphores without a locking protocol can be released
> by everyone, e.g. in contrast to the POSIX mutexes (all variants) or the
> Classic binary semphores with priority inheritance or ceiling there is no
> owner check in the release path.
>
> This behaviour is a bit unexpected and not documented.
>
> The following test case fails in case an owner check is added:
>
> {{{
> *** BEGIN OF TEST SP 42 ***
> Exercising blocking discipline w/extract in FIFO order
> Exercising blocking discipline w/unblock in FIFO order
> TA00 - unblocked - OK
>
> rtems_semaphore_delete FAILED -- expected (RTEMS_SUCCESSFUL) got
> (RTEMS_RESOURCE_IN_USE)
> }}}
>
> This is actually a bug in the test, since an available mutex is released
> again.

New description:

 The Classic binary semaphores without a locking protocol can be released
 by everyone, e.g. in contrast to the POSIX mutexes (all variants) or the
 Classic binary semphores with priority inheritance or ceiling, there is no
 owner check in the release path.

 This behaviour is a bit unexpected and not documented.

 The following test case fails in case an owner check is added:

 {{{
 *** BEGIN OF TEST SP 42 ***
 Exercising blocking discipline w/extract in FIFO order
 Exercising blocking discipline w/unblock in FIFO order
 TA00 - unblocked - OK

 rtems_semaphore_delete FAILED -- expected (RTEMS_SUCCESSFUL) got
 (RTEMS_RESOURCE_IN_USE)
 }}}

 This is actually a bug in the test, since an available mutex is released
 again.

--

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