[lkml]   [2009]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
    2009/8/8 Alan Stern <>:
    > On Fri, 7 Aug 2009, Peter Zijlstra wrote:

    >> It used to be that _all_ dev->sem instances were taken on suspend or
    >> something like that, I think that got fixed a long while back.
    >> I'd have to look at what the current locking requirements for dev->sem
    >> are.
    > It is supposed to be locked whenever the driver core invokes a probe,
    > remove, or PM-related callback.  Under some circumstances, the parent's
    > semaphore is supposed to be locked as well.  Individual subsystems may
    > have their own requirements in addition to these.
    > The ordering requirement is: Don't try to acquire a device's lock if
    > you already hold the lock for a non-ancestor device.  More generally
    > (if more obscurely): If you already hold device A's lock, then don't
    > try to acquire the lock for device B unless you already hold the lock
    > for A & B's most recent common ancestor.

    It seems that the following case is very common, and A and B have no
    common ancestor, but we can hold device A and B's lock at the same
    time, can't we?


    device A comes in one bus:
    ->device_attach():drivers/base/dd.c /*holding device A's lock*/
    ->...drv->probe() /*sleep here some time*/

    then device B comes in another bus:
    ->device_attach():drivers/base/dd.c /*holding device B's lock*/
    ->...drv->probe() /*sleep here some time*/

    Lei Ming
    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: 2009-08-08 11:09    [W:0.031 / U:0.972 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site