From 70f34fa1dd0f7ead9110316dff142ad8fa6ce499 Mon Sep 17 00:00:00 2001
From: Nicholas Mc Guire <der.herr@hofr.at>
Date: Sun, 15 Dec 2013 15:40:47 +0100
Subject: [PATCH 190/414] bad return value in __mutex_lock_check_stamp

Bad return value in _mutex_lock_check_stamp - this problem only would show
up with 3.12.1 rt4 applied but CONFIG_PREEMPT_RT_FULL not enabled
currently it would be returning what ever vprintk_emit ended up with
(atleast on x86), which probably is not the intended behavior. Added a
return 0; as in the case with CONFIG_PREEMPT_RT_FULL enabled.

Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
 kernel/rtmutex.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/rtmutex.c b/kernel/rtmutex.c
index d2cdfa6e0f22..f78bbcd8a01c 100644
--- a/kernel/rtmutex.c
+++ b/kernel/rtmutex.c
@@ -1128,6 +1128,7 @@ static inline int __sched
 __mutex_lock_check_stamp(struct rt_mutex *lock, struct ww_acquire_ctx *ctx)
 {
 	BUG();
+	return 0;
 }
 
 #endif
-- 
2.10.2

