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
..
api	tools lib fd array: Allow associating an integer cookie with each entry	2014-09-25 16:46:55 -03:00
lockdep	tools/liblockdep: Fix debug_check thinko in mutex destroy	2014-12-19 15:50:55 -05:00
symbol	tools lib symbol: Start carving out symbol parsing routines from perf	2013-12-13 10:30:20 -03:00
traceevent	tools lib traceevent: Fix a risk for doing free on uninitialized pointer	2014-06-27 11:14:47 +02:00