mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
	bpf@vger.kernel.org, dm-devel@lists.linux.dev,
	fsverity@lists.linux.dev, keyrings@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Alasdair Kergon <agk@redhat.com>,
	Alexei Starovoitov <ast@kernel.org>, Alex Shi <alexs@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Benjamin Marzinski <bmarzins@redhat.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Emil Tsalapatis <emil@etsalapatis.com>,
	Ignat Korchagin <ignat@linux.win>,
	Ihor Solodrai <ihor.solodrai@linux.dev>,
	James Morris <jmorris@namei.org>, Jiri Olsa <jolsa@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Mike Snitzer <snitzer@kernel.org>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Paul Moore <paul@paul-moore.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Song Liu <song@kernel.org>, "Theodore Y. Ts'o" <tytso@mit.edu>,
	Yanteng Si <si.yanteng@linux.dev>,
	Yonghong Song <yonghong.song@linux.dev>
Subject: Re: [PATCH v6 0/3] KEYS: Replace assoc_array with rhashtable
Date: Sat, 7 Nov 2026 12:42:10 -0800	[thread overview]
Message-ID: <20261107204210.GG6049@quark> (raw)
In-Reply-To: <au-FkAtC4Gcw7Bkb@kernel.org>

On Sat, Nov 07, 2026 at 10:09:52PM +0200, Jarkko Sakkinen wrote:
> On Sat, Nov 07, 2026 at 09:56:01PM +0200, Jarkko Sakkinen wrote:
> > The keyrings subsystem is the sole user of assoc_array. It has over 1700
> > lines of code, no test suite, and a long history of bugs, with LLMs now
> > finding more.
> > 
> > This unfortunate outcome has evolved over time by large from the shortage
> > of in-kernel callers, time bandwidth and 3rd party contributors.
> > 
> > What the keyrings subsystem needs is just a generic key-value store, which
> > performs well with sparse key sets. Replace assoc_array with an
> > rhashtable-backed keyring index and remove assoc_array from the kernel.
> 
> Sashiko: https://sashiko.dev/#/patchset/20261107195605.3929659-1-jarkko%40kernel.org
> 
> Not addressing this as only one patch changed and the change was
> exactly:
> 
> diff --git a/security/keys/keyring.c b/security/keys/keyring.c
> index 772fa0e35f9d..6761c6801edc 100644
> --- a/security/keys/keyring.c
> +++ b/security/keys/keyring.c
> @@ -12,7 +12,6 @@
>  #include <linux/security.h>
>  #include <linux/seq_file.h>
>  #include <linux/err.h>
> -#include <linux/delay.h>
>  #include <linux/jhash.h>
>  #include <linux/user_namespace.h>
>  #include <linux/nsproxy.h>
> @@ -101,6 +100,7 @@ static const struct rhashtable_params keyring_link_params = {
>         .min_size               = 4,
>         .nelem_hint             = 3,
>         .automatic_shrinking    = true,
> +       .insecure_elasticity    = true,
>  };
> 
>  static struct keyring_index *keyring_index_locked(const struct key *keyring)
> @@ -1225,12 +1225,8 @@ int __key_link_begin(struct key *keyring,
>                 if (ret < 0)
>                         goto error;
> 
> -               do {
> -                       ret = rhashtable_insert_fast(&links->ht, &link->node,
> -                                                    keyring_link_params);
> -                       if (ret == -EBUSY)
> -                               fsleep(100);
> -               } while (ret == -EBUSY);
> +               ret = rhashtable_insert_fast(&links->ht, &link->node,
> +                                            keyring_link_params);
>                 if (ret < 0) {
>                         key_payload_reserve(keyring,
>                                             keyring->datalen - KEYQUOTA_LINK_BYTES);
> 
> So I don't think there are any real issue with the patch set, except I
> will need to rebase the commits to the latest mainline.

It looks good to me now too, but it would be good to get a Sashiko run
on the latest version.  Sashiko hasn't run since v3, as it failed to
apply the series.  You should base the series on a commit in either
mainline or linux-next, and pass the '--base' option to 'git
format-patch' so it adds a 'base-commit' line.

(The only reason I've been able to apply it myself for review is that I
went out of my way to find your keys-rhashtable branch in git.)

- Eric

      reply	other threads:[~2026-11-07 20:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 19:56 Jarkko Sakkinen
2026-11-07 19:56 ` [PATCH v6 1/3] KEYS: Introduce keyring_is_empty() Jarkko Sakkinen
2026-11-07 19:56 ` [PATCH v6 2/3] KEYS: Replace assoc_array with rhashtable Jarkko Sakkinen
2026-11-07 19:56 ` [PATCH v6 3/3] lib: Remove assoc_array Jarkko Sakkinen
2026-11-07 20:09 ` [PATCH v6 0/3] KEYS: Replace assoc_array with rhashtable Jarkko Sakkinen
2026-11-07 20:42   ` Eric Biggers [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=20261107204210.GG6049@quark \
    --to=ebiggers@kernel.org \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexs@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bmarzins@redhat.com \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=dhowells@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=dzm91@hust.edu.cn \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=fsverity@lists.linux.dev \
    --cc=ignat@linux.win \
    --cc=ihor.solodrai@linux.dev \
    --cc=jarkko@kernel.org \
    --cc=jmorris@namei.org \
    --cc=jolsa@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=mpatocka@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=rdunlap@infradead.org \
    --cc=serge@hallyn.com \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=snitzer@kernel.org \
    --cc=song@kernel.org \
    --cc=tytso@mit.edu \
    --cc=yonghong.song@linux.dev \
    /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

all inboxes | Powered by JetHome®