lkml.org 
[lkml]   [2017]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] futex: move debug_rt_mutex_free_waiter() further down
    On 2017-03-08 16:29:02 [+0100], To Peter Zijlstra wrote:
    > Without this, futex_requeue_pi_signal_restart will trigger
    >
    > |kernel BUG at locking/rtmutex_common.h:55!
    > |Call Trace:
    > | rt_mutex_cleanup_proxy_lock+0x54/0x90
    > | futex_wait_requeue_pi.constprop.21+0x387/0x4d0
    > | do_futex+0x289/0xbf0
    > |RIP: remove_waiter+0x157/0x170 RSP: ffffc90000e0fbe0
    >
    > with BUG 2222222222222222 != pointer once this patch is applied.

    My wording is wrong. This BUG_ON() statement described here in this
    patch (together with the test case mentioned) will trigger once

    "[PATCH -v5 12/14] futex,rt_mutex: Restructure rt_mutex_finish_proxy_lock()"

    is applied.

    Sebastian

    \
     
     \ /
      Last update: 2017-03-08 16:40    [W:2.288 / U:0.088 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site