From: Jarkko Sakkinen <jarkko@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: "Jan Sebastian Götte" <linux@jaseg.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Baoquan He" <baoquan.he@linux.dev>,
"Mike Rapoport" <rppt@kernel.org>,
"Pasha Tatashin" <pasha.tatashin@soleen.com>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Dave Young" <ruirui.yang@linux.dev>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Mimi Zohar" <zohar@linux.ibm.com>,
"James Bottomley" <James.Bottomley@hansenpartnership.com>,
"Rob Herring" <robh@kernel.org>,
"Saravana Kannan" <saravanak@kernel.org>,
"Coiby Xu" <coxu@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, keyrings@vger.kernel.org,
linux-mm@kvack.org, linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH 4/4] security/keys: zeroize key payloads before kdump
Date: Mon, 10 Aug 2026 18:31:06 +0300 [thread overview]
Message-ID: <annuus46w5SXmlsA@kernel.org> (raw)
In-Reply-To: <2259835.1785538211@warthog.procyon.org.uk>
On Fri, Jul 31, 2026 at 11:50:11PM +0100, David Howells wrote:
> I've no particular objection to this, though I'd prefer the name 'wipe' to
> 'zeroize'.
LOL, I responded exactly same before reading your response :-)
So yeah, +1 to this.
>
> You should also wipe fscrypt, tls, rxrpc*, ceph and cifs spnego type keys and
> maybe asymmetric type keys.
>
> David
>
BR< Jarkko
next prev parent reply other threads:[~2026-08-10 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260731154608.153258-1-linux@jaseg.de>
2026-08-01 14:03 ` [PATCH 0/4] CRASH_ZEROIZE: Wipe secrets before kdump Baoquan He
2026-08-01 16:31 ` Jan Sebastian Götte
2026-08-02 5:08 ` Dave Young
2026-08-02 10:20 ` Jan Sebastian Götte
2026-08-03 12:12 ` Dave Young
2026-08-03 12:54 ` Jan Sebastian Götte
2026-08-03 9:59 ` David Howells
2026-08-03 12:00 ` Dave Young
[not found] ` <20260731154608.153258-3-linux@jaseg.de>
2026-08-05 4:19 ` [PATCH 2/4] kexec: add CRASH_ZEROIZE to wipe " sashiko-bot
2026-08-10 15:29 ` Jarkko Sakkinen
[not found] ` <20260731154608.153258-4-linux@jaseg.de>
2026-08-05 4:26 ` [PATCH 3/4] mm/secretmem: zeroize secret pages " sashiko-bot
[not found] ` <20260731154608.153258-5-linux@jaseg.de>
2026-08-05 4:29 ` [PATCH 4/4] security/keys: zeroize key payloads " sashiko-bot
[not found] ` <2259835.1785538211@warthog.procyon.org.uk>
2026-08-10 15:31 ` Jarkko Sakkinen [this message]
2026-07-31 16:27 [PATCH 0/4] CRASH_ZEROIZE: Wipe secrets " Jan Sebastian Götte
2026-07-31 16:27 ` [PATCH 4/4] security/keys: zeroize key payloads " Jan Sebastian Götte
2026-07-31 16:45 ` sashiko-bot
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=annuus46w5SXmlsA@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=coxu@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=kexec@lists.infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@jaseg.de \
--cc=pasha.tatashin@soleen.com \
--cc=paul@paul-moore.com \
--cc=pratyush@kernel.org \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=saravanak@kernel.org \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/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