Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
From: Alexander Potapenko <glider@google.com>
Date: 2019-06-27 13:17:14
Also in:
linux-mm
From: Alexander Potapenko <glider@google.com>
Date: 2019-06-27 13:17:14
Also in:
linux-mm
On Thu, Jun 27, 2019 at 1:28 AM Andrew Morton [off-list ref] wrote:
On Wed, 26 Jun 2019 14:19:42 +0200 Alexander Potapenko [off-list ref] wrote:quoted
v8: - addressed comments by Michal Hocko: revert kernel/kexec_core.c and apply initialization in dma_pool_free() - disable init_on_alloc/init_on_free if slab poisoning or page poisoning are enabled, as requested by Qian Cai - skip the redzone when initializing a freed heap object, as requested by Qian Cai and Kees Cook - use s->offset to address the freeptr (suggested by Kees Cook) - updated the patch description, added Signed-off-by: tagv8 failed to incorporate https://ozlabs.org/~akpm/mmots/broken-out/mm-security-introduce-init_on_alloc=1-and-init_on_free=1-boot-options-fix.patch and https://ozlabs.org/~akpm/mmots/broken-out/mm-security-introduce-init_on_alloc=1-and-init_on_free=1-boot-options-fix-2.patch it's conventional to incorporate such fixes when preparing a new version of a patch.
v9 contains these patches (I've also exported init_on_free), so should now be fine to drop them. -- Alexander Potapenko Software Engineer Google Germany GmbH Erika-Mann-Straße, 33 80636 München Geschäftsführer: Paul Manicle, Halimah DeLaine Prado Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg