Bug #1123
pthread_rwlock: wrong order on acquiring lock
Start date:
11/09/2015
Due date:
% Done:
0%
Estimated time:
CPU Architecture:
Host OS:
Toolchain:
Android version:
CrystaX Version:
Description
Use case:
- Main thread set its shcedule policy as "SCHED_FIFO", with highest priority: sched_get_priority_min()+3.
- Main thread write lock 'rwlock'
- Create a writer1 thread, with schedule policy as "SCHED_FIFO", and priority using sched_get_priority_min()+2. The writer should block.
- Create reader thread, with same priority as writer1. The reader should also block.
- Create a writer2 thread, with priority sched_get_priority_min(). It should block on write lock too.
- Main thread release the 'rwlock'
Expected order of lock:
- writer1
- reader
- writer2
Actual order:
- writer1
- writer2
- reader
Updated by Dmitry Moskalchuk almost 5 years ago
- Description updated (diff)
- CrystaX Version set to 10.3.1