[lkml]   [2010]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.6.34-rc1: rcu lockdep bug?
    On Thu, Mar 11, 2010 at 05:45:56AM -0800, Paul E. McKenney wrote:
    >On Thu, Mar 11, 2010 at 06:05:38PM +0800, Américo Wang wrote:
    >> Hello, Paul and Peter,
    >> Attached is the lockdep warning that I triggered today.
    >> I am not sure if this is a bug of rcu lockdep, because I am
    >> testing my patch when this occurred. However, in the backtrace,
    >> there is none of the functions that I touched, weird.
    >> So, please help to check if this is a bug of rcu lockdep.
    >This sort of thing is caused by acquiring the same lock with softirq
    >(AKA BH) blocked and not, which can result in self-deadlock.
    >There was such a bug in the RCU lockdep stuff in -tip, but it has long
    >since been fixed. If you were seeing that bug, rcu_do_batch() would
    >be on the stack, which it does not appear to be.
    >So does your patch involve the usbfs_mutex? Or attempt to manipulate
    >vfs/fs state from withing networking softirq/BH context?

    Nope, it is a patch for netpoll, nothing related with usb, nor vfs.

    Thanks much!

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2010-03-11 17:17    [W:0.020 / U:3.460 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site