From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH] KEYS: do not let an unmatched key decide the search result
Date: Sun, 08 Nov 2026 13:24:07 +0000 [thread overview]
Message-ID: <sashiko-outbox-203776@kernel.org> (raw)
In-Reply-To: <20261108131413.12012-2-weiguixiong@bytedance.com>
> KEYCTL_SEARCH returns -ENOKEY, -EKEYREVOKED, or -EKEYEXPIRED for the key
> selected by type and description. keyring_search_iterator() currently
> records revoked or expired state before asking the key type whether the key
> matches.
>
> Direct lookup visits the indexed description, so that ordering normally
> does not matter. Iterative lookup visits every key of the requested type,
> however. The in-tree asymmetric id/ex/dn lookups and dns_resolver use this
> mode. A revoked key with a different description can therefore make
> KEYCTL_SEARCH return -EKEYREVOKED instead of continuing the search. It can
> also prevent request_key_and_link() from issuing an upcall because that
> path only upcalls after -EAGAIN. An unmatched expired key similarly
> pollutes searches that do not set KEYRING_SEARCH_SKIP_EXPIRED; the request
> path itself sets that flag.
>
> Run the type comparator before recording state errors, so only a key that
> matches the caller's criterion can decide the search result.
>
> Fixes: b2a4df200d57 ("KEYS: Expand the capacity of a keyring")
> Signed-off-by: Guixiong Wei <weiguixiong@bytedance.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261108131413.12012-2-weiguixiong@bytedance.com?part=1
next prev parent reply other threads:[~2026-11-08 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 13:14 [PATCH] KEYS: do not let an unmatched key decide the search result Guixiong Wei
2026-11-08 13:24 ` sashiko-bot [this message]
2026-11-08 19:01 ` Jarkko Sakkinen
2026-11-09 1:10 ` Guixiong Wei
2026-11-09 1:17 ` 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=sashiko-outbox-203776@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.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 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.