Hi Patrick, On Sat, Jun 11, 2022 at 8:50 AM Patrick Wang <patrick.wang.shcn@xxxxxxxxx> wrote: > The kmemleak_*_phys() interface uses "min_low_pfn" and > "max_low_pfn" to check address. But on some architectures, > kmemleak_*_phys() is called before those two variables > initialized. The following steps will be taken: > > 1) Add OBJECT_PHYS flag and rbtree for the objects allocated > with physical address > 2) Store physical address in objects if allocated with OBJECT_PHYS > 3) Check the boundary when scan instead of in kmemleak_*_phys() Thanks for your series! > This patch set will solve: > https://lore.kernel.org/r/20220527032504.30341-1-yee.lee@xxxxxxxxxxxx > https://lore.kernel.org/r/9dd08bb5-f39e-53d8-f88d-bec598a08c93@xxxxxxxxx Thanks, this finally gets rid of the thousands of suspected memory leaks reported since commit 23c2d497de21f258 ("mm: kmemleak: take a full lowmem check in kmemleak_*_phys()") in v5.18-rc3 on my arm64 boards. Tested-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
