[PATCH v2] rtems: Fix no protocol mutex release

Sebastian Huber sebastian.huber at embedded-brains.de
Mon Jun 6 09:57:41 UTC 2016



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

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.




More information about the devel mailing list