On Thu, Jun 13, 2013 at 06:41:15PM -0400, Sasha Levin wrote: > liblockdep is a tiny wrapper built around kernel/lockdep.c. The aim is to > provide the same functionality the kernel gets from lockdep to userspace. > > The bulk of the code here is the LD_PRELOAD support which provides users > an easy way to test their code without having to integrate liblockdep into > said code. Simply doing: > > lockdep my_app > > Would provide lockdep support to my_app. > > There is also a small test suite to test both mutexes and rwlocks, it's > based on the tests in lib/locking-selftest.c. > > This entire patch series was reviewed by lockdep maintainers and accepted to > the tip tree previously. It was pulled out so that the potential merge of > liblockdep won't delay the rest of the commits in the tip locking tree. > > For some more background about this entire thing, the folks at LWN did > an awesome overview: http://lwn.net/Articles/536363/ >
Ingo, I don't think I see anything holding this back; however I remember reading some email about people not liking stuff like this living in the tools/ directory or such. Will you pick this up? -- 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/
