Kirill Smelkov 95bfdf23e4 tools/liblockdep: Fix debug_check thinko in mutex destroy ... In mutex destroy code currently we pass to debug_check_no_locks_freed() [mem_from, mem_end) address region. But debug_check_no_locks_freed() accepts mem_from, mem_*len* i.e. second parameter is region length, not end address. And it was always so, starting from 2006 (fbb9ce95 "lockdep: core"). Fix it, or else on a mutex destroy we wrongly check much-wider-than-mutex region and can find not-yet-released other locks there and wrongly report BUGs on them. Signed-off-by: Kirill Smelkov <kirr@nexedi.com> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>		2014-12-19 15:50:55 -05:00
..
include/liblockdep	tools/liblockdep: Account for bitfield changes in lockdeps lock_acquire	2014-07-07 12:20:16 -04:00
tests	liblockdep: Add pthread_rwlock_t test suite	2013-11-27 11:55:24 +01:00
uinclude	tools: Consolidate types.h	2014-05-01 21:22:39 +02:00
common.c
lockdep	liblockdep: Add the 'lockdep' user-space utility	2013-11-27 11:56:25 +01:00
lockdep_internals.h
lockdep_states.h
lockdep.c
Makefile	Merge branch 'perf-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip into next	2014-06-03 13:18:00 -07:00
preload.c	tools/liblockdep: Fix debug_check thinko in mutex destroy	2014-12-19 15:50:55 -05:00
rbtree.c
run_tests.sh	tools/liblockdep: Mark runtests.sh as executable	2014-02-26 21:21:59 -05:00