Re: [PATCH v2 01/13] kexec: add CRASH_WIPE_SECRETS to wipe secrets before kdump
Lukas Wunner <[email protected]>
| Newsgroups | gmane.linux.documentation,gmane.linux.kernel.kexec,gmane.linux.kernel,gmane.linux.ports.arm.kernel,gmane.linux.kernel.mm,gmane.linux.kernel.lsm,gmane.linux.kernel.cryptoapi,gmane.linux.nfs,gmane.linux.network,gmane.linux.file-systems |
|---|---|
| Message-ID | <[email protected]> |
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