The following commit has been merged into the locking/core branch of tip:

Commit-ID:     31120afb21f5892aa981af635b425a074e978cab
Gitweb:        
https://git.kernel.org/tip/31120afb21f5892aa981af635b425a074e978cab
Author:        Thomas Gleixner <[email protected]>
AuthorDate:    Tue, 23 Mar 2021 22:30:26 +01:00
Committer:     Ingo Molnar <[email protected]>
CommitterDate: Wed, 24 Mar 2021 08:06:07 +01:00

locking/rtmutex: Inline chainwalk depth check

There is no point for this wrapper at all.

Signed-off-by: Thomas Gleixner <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
---
 kernel/locking/rtmutex.c | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)

diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index a18ee0c..0eac57c 100644
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
@@ -343,14 +343,9 @@ static void rt_mutex_adjust_prio(struct task_struct *p)
 static bool rt_mutex_cond_detect_deadlock(struct rt_mutex_waiter *waiter,
                                          enum rtmutex_chainwalk chwalk)
 {
-       /*
-        * This is just a wrapper function for the following call,
-        * because debug_rt_mutex_detect_deadlock() smells like a magic
-        * debug feature and I wanted to keep the cond function in the
-        * main source file along with the comments instead of having
-        * two of the same in the headers.
-        */
-       return debug_rt_mutex_detect_deadlock(waiter, chwalk);
+       if (IS_ENABLED(CONFIG_DEBUG_RT_MUTEX))
+               return waiter != NULL;
+       return chwalk == RT_MUTEX_FULL_CHAINWALK;
 }
 
 /*

Reply via email to