Actions
Feature #3193
closed118: Correct use of reader-writer spinlocks
Start date:
07/12/2012
Due date:
% Done:
100%
Estimated time:
Published in build:
Description
A reader-writer lock is a spinlock, except you lock it in one of two modes: a `read lock' or a `write lock'. More than one people can share a `read lock', but the write lock is exclusive: if someone has a write lock, no one can have any lock.
- - multiple write locks are not permitted
- multiple write unlocks are not permitted
- - read lock is not permitted after write lock
- - read unlock is not permitted before read lock
- write unlock is not permitted before write lock
- - read and write locks must be free at the end
Updated by Ilya Shchepetkov over 12 years ago
- Status changed from Open to Resolved
- % Done changed from 40 to 100
Updated by Evgeny Novikov over 12 years ago
- Status changed from Resolved to Open
Make a reference to commits and branches where this rule model is implemented and then mark it as resolved.
Updated by Ilya Shchepetkov over 12 years ago
- Status changed from Open to Resolved
Fixed in commit b74928f of 118_1a branch and will be merged to master together with it.
Updated by Alexey Khoroshilov almost 11 years ago
- Status changed from Resolved to Open
There 3 false positives of 13 in 3.13-rc1 that can be handled by rerouter.
It makes sense to implement it.
Updated by Ilya Shchepetkov over 10 years ago
Rerouter version of this model was implemented in rule118-tmpl branch.
The above three false positives are gone.
Updated by Evgeny Novikov about 10 years ago
- Status changed from Open to Closed
There are 10 false alarms for all kernel modules, 9 is due to seq_operations.
Actions