From: Jarkko Sakkinen <jarkko@kernel.org>
To: keyrings@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Mimi Zohar <zohar@linux.ibm.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [RFC PATCH v2] KEYS: Add a list for unreferenced keys
Date: Mon, 31 Mar 2025 20:48:27 +0300 [thread overview]
Message-ID: <Z-rVa23rud62nyQN@kernel.org> (raw)
In-Reply-To: <20250330111649.13547-1-jarkko@kernel.org>
On Sun, Mar 30, 2025 at 02:16:49PM +0300, Jarkko Sakkinen wrote:
> Add an isolated list for unreferenced keys. This splits key deletion as
> separate phase, after the key reaper. This makes the whole process more
> rigid, as these two distinct tasks don't intervene each other.
>
> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
> ---
> v2:
> - Rename key_gc_unused_keys as key_gc_graveyard, and re-document the
> function.
> ---
> include/linux/key.h | 1 -
> security/keys/gc.c | 27 +++++++--------------------
> security/keys/internal.h | 1 +
> security/keys/key.c | 7 +++++--
> 4 files changed, 13 insertions(+), 23 deletions(-)
kernel-test-bot reported:
https://lore.kernel.org/oe-lkp/202503312252.bef52733-lkp@intel.com/
I.e., v3 is coming.
BR, Jarkko
prev parent reply other threads:[~2025-03-31 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 11:16 [RFC PATCH v2] KEYS: Add a list for unreferenced keys Jarkko Sakkinen
2025-03-30 11:22 ` Jarkko Sakkinen
2025-03-31 17:48 ` Jarkko Sakkinen [this message]
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=Z-rVa23rud62nyQN@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.