summaryrefslogtreecommitdiff
path: root/kernel/rtmutex.c
diff options
context:
space:
mode:
authorNicholas Mc Guire <der.herr@hofr.at>2013-12-15 14:40:47 (GMT)
committerScott Wood <scottwood@freescale.com>2015-02-13 22:20:46 (GMT)
commit26dae1390c2fe9932071d1f491908255cb85a718 (patch)
tree55e7d9ba6a84ef4683855a9e3bb7c61a6ea9d669 /kernel/rtmutex.c
parent72cd02dbf45da9eac4553d1c7d572b85979635e8 (diff)
downloadlinux-fsl-qoriq-26dae1390c2fe9932071d1f491908255cb85a718.tar.xz
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>
Diffstat (limited to 'kernel/rtmutex.c')
-rw-r--r--kernel/rtmutex.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/kernel/rtmutex.c b/kernel/rtmutex.c
index d2cdfa6..f78bbcd 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