From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v12 2/6] s390/cert_store: Return an owned reference from find_cs_keyring()
Date: Sat, 14 Nov 2026 16:53:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-214790@kernel.org> (raw)
In-Reply-To: <20261114164139.429814-3-jarkko@kernel.org>
> Return an owned reference from find_cs_keyring() so that it will not get
> dropped.
>
> Cc: David Howells <dhowells@redhat.com>
> Cc: stable@vger.kernel.org # v6.6+
> Fixes: 8cf57d7217c3 ("s390: add support for user-defined certificates")
> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261114164139.429814-1-jarkko@kernel.org?part=2
next prev parent reply other threads:[~2026-11-14 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 16:41 [PATCH v12 0/6] KEYS: Replace assoc_array with rhashtable Jarkko Sakkinen
2026-11-14 16:41 ` [PATCH v12 1/6] s390/cert_store: Pin the user session keyring Jarkko Sakkinen
2026-11-14 16:58 ` sashiko-bot
2026-11-14 16:41 ` [PATCH v12 2/6] s390/cert_store: Return an owned reference from find_cs_keyring() Jarkko Sakkinen
2026-11-14 16:53 ` sashiko-bot [this message]
2026-11-14 16:41 ` [PATCH v12 3/6] s390/cert_store: Skip keys that disappeared during invalidation Jarkko Sakkinen
2026-11-14 17:01 ` sashiko-bot
2026-11-14 16:41 ` [PATCH v12 4/6] KEYS: Introduce keyring_is_empty() Jarkko Sakkinen
2026-11-14 16:46 ` sashiko-bot
2026-11-14 16:41 ` [PATCH v12 5/6] KEYS: Replace assoc_array with rhashtable Jarkko Sakkinen
2026-11-14 17:01 ` sashiko-bot
2026-11-14 16:41 ` [PATCH v12 6/6] lib: Remove assoc_array Jarkko Sakkinen
2026-11-14 16:49 ` sashiko-bot
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-214790@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox