On Tue, Aug 11, 2026 at 09:38:20PM +0200, Jan Sebastian Götte wrote: > > Could you perhaps narrow the scope to one or two things that actually > > are useful and can reasonably be supported for the application? For > > example, secretmem seems to be the only thing you mentioned that you're > > actually planning to use. > > I'm open to whittling down the scope of this series. In my use case I need > at least secretmem as well as dm-crypt, which then pulls in the crypto tfm > stuff. Personally, I could live without the other bits, I just thought > they'd be easy enough to include.
Please do reduce the scope. Note that even if dm-crypt is in scope, "crypto: api - wipe tfm contexts before kdump" is neither required nor sufficient. For one, dm-crypt has its own copy of the key. The wiping should be done by the kernel feature(s) that need it, as they know what actually needs to be wiped, and they can do so without the bottleneck of a new global list. - Eric
