On Wed, Jun 8, 2022 at 10:46 AM Kuan-Ying Lee <Kuan-Ying.Lee@xxxxxxxxxxxx> wrote: > > On Fri, 2022-06-03 at 11:54 +0800, Patrick Wang 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() > > > > 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 > > Hi Patrick, > > If this patchset fix the above issue, I think we need to add > the below fixes tag. > > Fixes: 23c2d497de21 ("mm: kmemleak: take a full lowmem check in > kmemleak_*_phys()") Hi Kuan-Ying, Thanks for taking a look. This series should solve the false positive on ppc32 and arm64. And the false positive on arm64 is triggered by commit 23c2d497de21. So I will add the fixes tag. Thanks, Patrick
