[PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options

Andrew Morton akpm at linux-foundation.org
Mon Jun 17 22:10:27 UTC 2019


On Mon, 17 Jun 2019 17:10:49 +0200 Alexander Potapenko <glider at google.com> wrote:

> Slowdown for the new features compared to init_on_free=0,
> init_on_alloc=0:
> 
> hackbench, init_on_free=1:  +7.62% sys time (st.err 0.74%)
> hackbench, init_on_alloc=1: +7.75% sys time (st.err 2.14%)

Sanity check time.  Is anyone really going to use this?  Seriously,
honestly, for real?  If "yes" then how did we determine that?

Also, a bit of a nit: "init_on_alloc" and "init_on_free" aren't very
well chosen names for the boot options - they could refer to any kernel
object at all, really.  init_pages_on_alloc would be better?  I don't think
this matters much - the boot options are already chaotic.  But still...




More information about the Linux-security-module-archive mailing list