lkml.org 
[lkml]   [2007]   [Mar]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[PATCH] lockdep: lockdep_depth vs. debug_locks Re: [2.6.20] BUG: workqueue leaked lock

    Here is some joke:

    [PATCH] lockdep: lockdep_depth vs. debug_locks

    lockdep really shouldn't be used when debug_locks == 0!


    Reported-by: Folkert van Heusden <folkert@vanheusden.com>
    Inspired-by: Oleg Nesterov <oleg@tv-sign.ru>
    Signed-off-by: Jarek Poplawski <jarkao2@o2.pl>

    ---

    diff -Nurp 2.6.21-rc4-git4-/include/linux/lockdep.h 2.6.21-rc4-git4/include/linux/lockdep.h
    --- 2.6.21-rc4-git4-/include/linux/lockdep.h 2007-03-20 20:24:17.000000000 +0100
    +++ 2.6.21-rc4-git4/include/linux/lockdep.h 2007-03-21 22:32:41.000000000 +0100
    @@ -245,7 +245,7 @@ extern void lock_release(struct lockdep_

    # define INIT_LOCKDEP .lockdep_recursion = 0,

    -#define lockdep_depth(tsk) ((tsk)->lockdep_depth)
    +#define lockdep_depth(tsk) (debug_locks ? (tsk)->lockdep_depth : 0)

    #else /* !LOCKDEP */

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/
    \
     
     \ /
      Last update: 2007-03-22 07:11    [W:0.019 / U:121.004 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site