lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <1556029006.6132.1.camel@lca.pw> Date: Tue, 23 Apr 2019 10:16:46 -0400 From: Qian Cai <cai@....pw> To: Borislav Petkov <bp@...en8.de>, Catalin Marinas <catalin.marinas@....com> Cc: dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org, tglx@...utronix.de, mingo@...hat.com, x86@...nel.org, linux-kernel@...r.kernel.org, Brijesh Singh <brijesh.singh@....com> Subject: Re: [PATCH] x86/mm/mem_encrypt: fix a crash with kmemleak_scan 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.
Powered by blists - more mailing lists