On Thu, Jul 10, 2014 at 03:02:29PM -0400, Sasha Levin wrote: > What if we move lockdep's acquisition point to after it actually got the > lock?
NAK, you want to do deadlock detection _before_ you're stuck in a deadlock. > We'd miss deadlocks, but we don't care about them right now. Anyways, doesn't > lockdep have anything built in to allow us to separate between locks which > we attempt to acquire and locks that are actually acquired? > > (cc PeterZ) > > We can treat locks that are in the process of being acquired the same as > acquired locks to avoid races, but when we print something out it would > be nice to have annotation of the read state of the lock. I'm missing the problem here I think. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
