From: Jarkko Sakkinen <jarkko@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>,
Roberto Sassu <roberto.sassu@huawei.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Eric Snowberg <eric.snowberg@oracle.com>,
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>,
"open list:KEYS/KEYRINGS" <keyrings@vger.kernel.org>
Subject: Re: [PATCH v6] KEYS: key_garbage_collector(): process in chunks
Date: Fri, 30 Oct 2026 22:03:42 +0200 [thread overview]
Message-ID: <auT4HmJImLQHmsTk@kernel.org> (raw)
In-Reply-To: <auTKovajh5MQlbre@kernel.org>
On Fri, Oct 30, 2026 at 06:49:45PM +0200, Jarkko Sakkinen wrote:
> Interesting :-) It has been idential other than block size change
> for v4, v5 and v6 and updating benchmark result but this is the
> first version with Sashiko feedback.
>
> Looking into it...
Couple of things:
1. Sashiko reported issue, which would result key_gc_schedule_links()
call in the place of key_gc_schedule_work().
2. I think it would be best if flags were set in the expired case
with a single atomic operation, which does not realize now when
key_gc_schedule_links()->key_gc_schedule_work() call path is
used.
I'll address the both issues.
Br, Jarkko
prev parent reply other threads:[~2026-10-30 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 16:09 [PATCH v6] KEYS: key_garbage_collector(): process in chunks Jarkko Sakkinen
2026-10-30 16:24 ` sashiko-bot
2026-10-30 16:49 ` Jarkko Sakkinen
2026-10-30 20:03 ` 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=auT4HmJImLQHmsTk@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=ebiggers@kernel.org \
--cc=eric.snowberg@oracle.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=roberto.sassu@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox