lkml.org 
[lkml]   [2021]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.13 143/151] locking/rtmutex: Use the correct rtmutex debugging config option
    Date
    From: Zhen Lei <thunder.leizhen@huawei.com>

    commit 07d25971b220e477eb019fcb520a9f2e3ac966af upstream.

    It's CONFIG_DEBUG_RT_MUTEXES not CONFIG_DEBUG_RT_MUTEX.

    Fixes: f7efc4799f81 ("locking/rtmutex: Inline chainwalk depth check")
    Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Acked-by: Will Deacon <will@kernel.org>
    Acked-by: Boqun Feng <boqun.feng@gmail.com>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20210731123011.4555-1-thunder.leizhen@huawei.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    ---
    kernel/locking/rtmutex.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    --- a/kernel/locking/rtmutex.c
    +++ b/kernel/locking/rtmutex.c
    @@ -343,7 +343,7 @@ static __always_inline bool
    rt_mutex_cond_detect_deadlock(struct rt_mutex_waiter *waiter,
    enum rtmutex_chainwalk chwalk)
    {
    - if (IS_ENABLED(CONFIG_DEBUG_RT_MUTEX))
    + if (IS_ENABLED(CONFIG_DEBUG_RT_MUTEXES))
    return waiter != NULL;
    return chwalk == RT_MUTEX_FULL_CHAINWALK;
    }

    \
     
     \ /
      Last update: 2021-08-16 15:32    [W:4.074 / U:0.176 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site