> A tfm's context holds the expanded key schedule, which a crash dump > would capture. > > Allocate tfms from the secret pool, so that their backing pages are > marked by crash_memaction for the kdump kernel to wipe. > The context is a flexible array at the end of struct crypto_tfm and the > frontend's private data sits in front of the struct, so the whole > allocation moves into the pool. > > Allocation cost increases by a bucket lookup in crash_memaction. Freeing > is unchanged. > > Signed-off-by: Jan Sebastian Götte <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great! -- Sashiko AI review · https://sashiko.dev/#/patchset/20260928-crash-memaction-upstream-20260921-v3-0-e511e9ee2...@jaseg.de?part=6
