Messages in this thread | | | Date | Fri, 15 Feb 2019 14:07:49 +0000 | From | Catalin Marinas <> | Subject | Re: [PATCH v2 3/5] kmemleak: account for tagged pointers when calculating pointer range |
| |
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 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@google.com>
I reviewed the old series. This patch also looks fine:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
| |