[lkml]   [2007]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectTwo unclear places in lockdep-design.txt
Hello, Ingo!

Many thanks for the lockdep validator! It has helped me immensely.
However, lockdep-design.txt has been pretty hard to read for me.

It would be great if you find an opportunity to clarify two things in
the documentation.

1) What is a lock dependency? What does "L1 -> L2" mean? Does it mean
that L1 should be first or second to be acquired?

2) What is "ever held with hardirqs enabled"? Does it mean that the
lock was used in the code where hardirqs were enabled, or that it _also_
didn't disable hardirqs by itself (e.g. by spin_lock_irq)? I suspect
the later is the case.

I wish I could submit a patch for the documentation, but I still don't
understand much of the theory. Still, I was able to interpret the error
messages in a way that allows me to fix the locking issues in some

Pavel Roskin

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: 2007-02-15 03:39    [W:0.015 / U:7.100 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site