tools/liblockdep: Fix debug_check thinko in mutex destroy
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 <b0eeaac46e675e9f95bf68c0df1041cf581c26f4@nexedi.com>
Signed-off-by: Sasha Levin <e642b69ed2fc111e09ffdc37feb733a52253340d@oracle.com>

KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs