Re: lockdep problem conversion semaphore->mutex (dev->sem)

On Sat, 2007-12-08 at 18:11 +0100, Peter Zijlstra wrote:

> > It must be the locking in __driver_attach(), taking dev->parent->sem
> > then taking dev->sem .. Assuming those are different structures, why
> > does lockdep trigger?
> 
> They aren't different, parent is a struct device again.

It's different memory tho .. I wasn't sure how to term that .. The locks
are in two different memory location so it couldn't be recursive .. I'm
only asking for my own understanding .. I don't mind inspecting
potentially bad locking ..

Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: lockdep problem conversion semaphore->mutex (dev->sem)
    • From: Peter Zijlstra <[email protected]>

• References:
  • lockdep problem conversion semaphore->mutex (dev->sem)
    • From: "Remy Bohmer" <[email protected]>
  • Re: lockdep problem conversion semaphore->mutex (dev->sem)
    • From: Peter Zijlstra <[email protected]>
  • Re: lockdep problem conversion semaphore->mutex (dev->sem)
    • From: Daniel Walker <[email protected]>
  • Re: lockdep problem conversion semaphore->mutex (dev->sem)
    • From: Peter Zijlstra <[email protected]>

• Prev by Date: Re: [PATCH 2.6.24-rc4] proc: Remove/Fix proc generic d_revalidate
• Next by Date: Re: programs vanish with 2.6.22+
• Previous by thread: Re: lockdep problem conversion semaphore->mutex (dev->sem)
• Next by thread: Re: lockdep problem conversion semaphore->mutex (dev->sem)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]