Re: [PATCH v2 3/5] kmemleak: account for tagged pointers when calculating pointer range

2019-02-15 Thread Catalin Marinas
On Wed, Feb 13, 2019 at 02:58:28PM +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

Re: [PATCH v2 3/5] kmemleak: account for tagged pointers when calculating pointer range

2019-02-13 Thread Qian Cai
On Wed, 2019-02-13 at 14:58 +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

[PATCH v2 3/5] kmemleak: account for tagged pointers when calculating pointer range

2019-02-13 Thread Andrey Konovalov
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