Re: [PATCH v2] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

On Wednesday 17 August 2016 02:58 PM, Catalin Marinas wrote: > Some of the kmemleak_*() callbacks in memblock, bootmem, CMA convert a > physical address to a virtual one using __va(). However, such physical > addresses may sometimes be located in highmem and using __va() is > incorrect, leading

Re: [PATCH v2] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

On Wednesday 17 August 2016 02:58 PM, Catalin Marinas wrote: > Some of the kmemleak_*() callbacks in memblock, bootmem, CMA convert a > physical address to a virtual one using __va(). However, such physical > addresses may sometimes be located in highmem and using __va() is > incorrect, leading

[PATCH v2] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

Some of the kmemleak_*() callbacks in memblock, bootmem, CMA convert a physical address to a virtual one using __va(). However, such physical addresses may sometimes be located in highmem and using __va() is incorrect, leading to inconsistent object tracking in kmemleak. The following functions

[PATCH v2] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

Some of the kmemleak_*() callbacks in memblock, bootmem, CMA convert a physical address to a virtual one using __va(). However, such physical addresses may sometimes be located in highmem and using __va() is incorrect, leading to inconsistent object tracking in kmemleak. The following functions