From: Eric Biggers <ebiggers@kernel.org>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"open list:SECURITY SUBSYSTEM"
<linux-security-module@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] KEYS: rhashtable bug fixes
Date: Wed, 21 Oct 2026 20:03:27 +0000 [thread overview]
Message-ID: <20261021200327.GA2210933@google.com> (raw)
In-Reply-To: <atkTgEwRQfh94zeV@kernel.org>
On Wed, Oct 21, 2026 at 10:33:20PM +0300, Jarkko Sakkinen wrote:
> On Tue, Oct 20, 2026 at 08:43:18PM +0300, Jarkko Sakkinen wrote:
> > My patch set that migrates assoc_array to rhashtable had some LLM
> > scavegend bug fixes. Unfortunately most them where either plain wrong or
> > not in the right scope. The bug fixes in this patch set are by human
> > labour constructed fully but they are derived from what I got out of the
> > original LLM source. Thus, they are tagged as LLM assisted.
>
> I guess these are ready to be merged? Eric do you have something for
> this revision? I already sent -rc1 pull request i.e., I don't mind
> to update it if necessary but otherwise I rather would just apply
> these.
Looks okay now.
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
- Eric
next prev parent reply other threads:[~2026-10-21 20:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 17:43 [PATCH v4 0/3] KEYS: rhashtable bug fixes Jarkko Sakkinen
2026-10-20 17:43 ` [PATCH v4 1/3] KEYS: Expand key->{datalen,quotalen} to unsigned int Jarkko Sakkinen
2026-10-20 17:53 ` sashiko-bot
2026-10-20 20:49 ` Jarkko Sakkinen
2026-10-20 20:59 ` Jarkko Sakkinen
2026-10-20 21:43 ` Eric Biggers
2026-10-20 22:01 ` Jarkko Sakkinen
2026-10-21 17:03 ` Eric Biggers
2026-10-21 17:14 ` Jarkko Sakkinen
2026-10-20 17:43 ` [PATCH v4 2/3] KEYS: Reject descriptions larger than KEY_MAX_DESC_SIZE Jarkko Sakkinen
2026-10-20 17:49 ` sashiko-bot
2026-10-20 21:16 ` Jarkko Sakkinen
2026-10-20 21:18 ` Jarkko Sakkinen
2026-10-20 17:43 ` [PATCH v4 3/3] KEYS: Verify the key identity in __key_unlink_begin Jarkko Sakkinen
2026-10-20 17:46 ` sashiko-bot
2026-10-21 19:33 ` [PATCH v4 0/3] KEYS: rhashtable bug fixes Jarkko Sakkinen
2026-10-21 20:03 ` Eric Biggers [this message]
2026-10-21 21:07 ` Jarkko Sakkinen
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=20261021200327.GA2210933@google.com \
--to=ebiggers@kernel.org \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@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 \
/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.