Messages in this thread | | | Subject | Re: [PATCH] x86/mm/mem_encrypt: fix a crash with kmemleak_scan | From | Qian Cai <> | Date | Tue, 23 Apr 2019 10:16:46 -0400 |
| |
On Tue, 2019-04-23 at 15:25 +0200, Borislav Petkov wrote: > So I guess free_init_pages() should be somehow telling kmemleak, "hey, > just freed that object, pls adjust your tracking lists" no? > > Because, otherwise, if we start sprinkling those kmemleak_free_part() > calls everywhere, that'll quickly turn into a game of whack-a-mole. And > we don't need that especially if kmemleak can easily be taught to handle > such cases.
In reality, this is only the second place that needs this kmemleak_free_part() call for all those years since kmemleak was born.
| |