From: Kirill Smelkov <kirr@nexedi.com>
Date: Mon, 8 Dec 2014 11:07:59 +0000 (+0300)
Subject: tools/liblockdep: Fix debug_check thinko in mutex destroy
X-Git-Tag: omap-for-v4.1/prcm-dts-mfd-syscon-fix~299^2^2^2
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=95bfdf23e4d59099340c01064f39e7f6875c02bc;p=pandora-kernel.git

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>
---

Reading git-diff-tree failed