[PATCH v2] rtems: Fix no protocol mutex release

[Chris Johns]

On 06/06/2016 19:57, Sebastian Huber wrote:
> On 04/06/16 08:16, Chris Johns wrote:
>> On 03/06/2016 23:44, Sebastian Huber wrote:
>>> On 03/06/16 15:40, Joel Sherrill wrote:
>>>> My concern is that this will break existing programs that used them for
>>>> condition synchronization.
>>>
>>> These applications are broken since you can obtain the
>>> RTEMS_BINARY_SEMAPHORE recursively.
>>>
>>
>> Did you check if there are any cases in the rtems source?
>
> A pure RTEMS_BINARY_SEMAPHORE is almost always a bug if you use a
> priority based scheduler. Interestingly, several parts in RTEMS used
> such a thing.
>
> https://devel.rtems.org/ticket/1452
> https://devel.rtems.org/ticket/2726
> https://devel.rtems.org/ticket/2727
> https://devel.rtems.org/ticket/2728
> https://devel.rtems.org/ticket/2729
>

Thanks for checking and fixing these.

Chris