Actions
Feature #4485
open154: incorrect usage of wwmutex interface
Status:
New
Priority:
Normal
Assignee:
-
Start date:
09/21/2013
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
Wait/Wound Deadlock-Proof Mutex Design is presented here:
http://lwn.net/Articles/548921/
- Forgetting to call ww_acquire_fini or ww_acquire_init.
- Attempting to lock more mutexes after ww_acquire_done.
- Attempting to lock more mutexes after -EDEADLK, before calling ww_mutex_lock_slow.
- Calling ww_mutex_lock_slow with while still holding some mutexes.
- Calling ww_mutex_lock_slow on the wrong mutex, or before -EDEADLK was returned.
- Unlocking mutexes with the wrong unlock function.
- Calling one of the ww_acquire_* twice on the same context.
- Using a different ww_class for the mutex than for the ww_acquire_ctx.
- Calling ww_acquire_init to initialize a second ww_acquire_ctx before having called ww_acquire_fini on the first.
- Mixing ww_mutex_lock and ww_mutex_lock_single.
Actions