On Tue, 5 Jul 2022 19:31:58 +0800 Patrick Wang <patrick.wang.shcn@xxxxxxxxx> wrote: > Kmemleak recently added a rbtree to store the objects > allocted with physical address. Those objects can't be > freed with kmemleak_free(). Use kmemleak_ignore_phys() > instead of kmemleak_free() for those objects. Thanks. What are the user-visible runtime effects of this? And are we able to identify a commit for the Fixes: line?
