True. sem_post should fail if priority inheritance is enabled and the caller is not a holder of a semaphore count. That check should be added. Certainly it is not a justification for eliminating core functionality.BTW, https://github.com/apache/nuttx/pull/5070 report that the system will crash if the priority inheritance enabled semaphore is waited or posted from different threads.
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Re: [Breaking change] Move nxmutex to sched Petro Karashchenko
- Re: [Breaking change] Move nxmutex to sched Petro Karashchenko
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Re: [Breaking change] Move nxmutex to sched Xiang Xiao
- Re: [Breaking change] Move nxmutex to sched Xiang Xiao
- Re: [Breaking change] Move nxmutex to sched Petro Karashchenko
- Re: [Breaking change] Move nxmutex to sched Xiang Xiao
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Re: [Breaking change] Move nxmutex to sched Fotis Panagiotopoulos
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Re: [Breaking change] Move nxmutex to sched David S. Alessio
- Re: [Breaking change] Move nxmutex to sched David S. Alessio
- Re: [Breaking change] Move nxmutex to sched Petro Karashchenko
- Re: [Breaking change] Move nxmutex to sched zyfeier
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt
- Re: [Breaking change] Move nxmutex to sched Petro Karashchenko
- Re: [Breaking change] Move nxmutex to sched Tomek CEDRO
- Re: [Breaking change] Move nxmutex to sched Gregory Nutt