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
..
cgroup
firewire
hv
include
lguest
lib	tools/liblockdep: Fix debug_check thinko in mutex destroy	2014-12-19 15:50:55 -05:00
net
nfsd
perf	perf probe: Trivial typo fix for --demangle	2014-10-29 10:30:18 -02:00
power	ACPICA: acpiexec: Do not put STDIN into raw mode unless it is a terminal.	2014-10-21 00:39:40 +02:00
scripts
testing	Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net	2014-11-13 17:54:08 -08:00
thermal/tmon
time
usb
virtio
vm
Makefile