From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/5] hardening: support zeroing all malloc buffers by default
Date: Thu, 28 Nov 2024 10:08:16 +0100 [thread overview]
Message-ID: <Z0gzAEmURo3Iv5Cn@pengutronix.de> (raw)
In-Reply-To: <20241125152024.477375-3-a.fatoum@pengutronix.de>
On Mon, Nov 25, 2024 at 04:20:21PM +0100, Ahmad Fatoum wrote:
> dummy malloc doesn't free and all allocations are in freshly sbrk()'d
> memory, which already zero.
>
> +config INIT_ON_ALLOC_DEFAULT_ON
> + bool "Enable heap memory zeroing on allocation by default"
> + depends on !MALLOC_LIBC
> + help
> + This has the effect of setting "init_on_alloc=1" on the kernel
> + command line. This can be disabled with "init_on_alloc=0".
> + When "init_on_alloc" is enabled, all page allocator and slab
> + allocator memory will be zeroed when allocated, eliminating
> + many kinds of "uninitialized heap memory" flaws, especially
> + heap content exposures. The performance impact varies by
> + workload, but most cases see <1% impact. Some synthetic
> + workloads have measured as high as 7%.
> +
> +config INIT_ON_FREE_DEFAULT_ON
> + bool "Enable heap memory zeroing on free by default"
> + depends on !MALLOC_DUMMY && !MALLOC_LIBC
> + help
> + This has the effect of setting "init_on_free=1" on the kernel
> + command line. This can be disabled with "init_on_free=0".
> + Similar to "init_on_alloc", when "init_on_free" is enabled,
> + all page allocator and slab allocator memory will be zeroed
> + when freed, eliminating many kinds of "uninitialized heap memory"
> + flaws, especially heap content exposures. The primary difference
> + with "init_on_free" is that data lifetime in memory is reduced,
> + as anything freed is wiped immediately, making live forensics or
> + cold boot memory attacks unable to recover freed memory contents.
> + The performance impact varies by workload, but is more expensive
> + than "init_on_alloc" due to the negative cache effects of
> + touching "cold" memory areas. Most cases see 3-5% impact. Some
> + synthetic workloads have measured as high as 8%.
These verbatim copies of the kernel help texts do not seem appropriate
for barebox.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-11-28 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 15:20 [PATCH 0/5] malloc: add options to zero-initialize buffers Ahmad Fatoum
2024-11-25 15:20 ` [PATCH 1/5] dlmalloc: add aliases with dl as prefix Ahmad Fatoum
2024-11-25 15:20 ` [PATCH 2/5] hardening: support zeroing all malloc buffers by default Ahmad Fatoum
2024-11-28 9:08 ` Sascha Hauer [this message]
2024-11-28 9:23 ` Ahmad Fatoum
2024-11-25 15:20 ` [PATCH 3/5] hardening: support initializing stack variables " Ahmad Fatoum
2024-11-25 15:20 ` [PATCH 4/5] kbuild: support register zeroing on function exit Ahmad Fatoum
2024-11-25 15:20 ` [PATCH 5/5] tlsf: panic in asserts if CONFIG_BUG_ON_DATA_CORRUPTION=y Ahmad Fatoum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z0gzAEmURo3Iv5Cn@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox