Re: [PATCH v2 01/13] kexec: add CRASH_WIPE_SECRETS to wipe secrets before kdump

From
Lukas Wunner <lukas@wunner.de>
Date
2026-08-16 12:13:39
Also in
dm-devel, kexec, keyrings, linux-crypto, linux-doc, linux-fscrypt, linux-fsdevel, linux-integrity, linux-mm, linux-nfs, linux-nvme, linux-security-module, lkml
Reply to
Jan Sebastian Götte, 2026-08-12
On Wed, Aug 12, 2026 at 12:08:39PM +0200, Jan Sebastian Götte wrote:
I can imagine one alternative way to approach this, tell me what you think:
Instead of registering wipe handlers that memzero places on panic, I could
put an optional registry of (addr, len) descriptors into crashkernel memory
that the original kernel populates with the PAs of buffers to clear ahead of
time. Then the kdump kernel could do the actual memzero. This would remove
all code from the actual kdump path here. The registry could be made
per-core to avoid locks.
Or create a dedicated mempool from which all sensitive data is allocated,
then call mempool_free_bulk() on kexec to poison everything in that pool?

Thanks,

Lukas
Thread (25 messages) 25 messages, 6 authors, last reply 2026-08-18
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help