Messages in this thread Patch in this message | ![/](/images/icornerl.gif) | | Date | Tue, 8 Mar 2016 14:05:39 -0800 | From | Davidlohr Bueso <> | Subject | [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock |
| |
The very nature of rt_mutex_handle_deadlock() implies that this patch is merely a formality, as in practice the saved barrier is of little use. That said, we can relax setting the task state and be done with it; blocking unconditionally... this is a deadlock!
Signed-off-by: Davidlohr Bueso <dbueso@suse.de> --- kernel/locking/rtmutex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c index 8eb99b7f1ac8..c3d3c8e8ea5c 100644 --- a/kernel/locking/rtmutex.c +++ b/kernel/locking/rtmutex.c @@ -1216,7 +1216,7 @@ static void rt_mutex_handle_deadlock(int res, int detect_deadlock, */ rt_mutex_print_deadlock(w); while (1) { - set_current_state(TASK_INTERRUPTIBLE); + __set_current_state(TASK_INTERRUPTIBLE); schedule(); } } -- 2.1.4
| ![\](/images/icornerr.gif) |