Re: [PATCH 3/5] kmemleak: account for tagged pointers when calculating pointer range
From: Catalin Marinas
Date: Fri Feb 15 2019 - 09:05:48 EST
On Mon, Feb 11, 2019 at 10:59:52PM +0100, Andrey Konovalov wrote:
> kmemleak keeps two global variables, min_addr and max_addr, which store
> the range of valid (encountered by kmemleak) pointer values, which it
> later uses to speed up pointer lookup when scanning blocks.
> With tagged pointers this range will get bigger than it needs to be.
> This patch makes kmemleak untag pointers before saving them to min_addr
> and max_addr and when performing a lookup.
> Signed-off-by: Andrey Konovalov <andreyknvl@xxxxxxxxxx>
Acked-by: Catalin Marinas <catalin.marinas@xxxxxxx>