From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Coiby Xu <coiby.xu@gmail.com>, kexec@lists.infradead.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <baoquan.he@linux.dev>,
Dave Young <ruirui.yang@linux.dev>,
Pratyush Yadav <pratyush@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 08/10] crash_dump: Check the function return codes in restore_dm_crypt_keys_to_thread_keyring
Date: Wed, 5 Aug 2026 17:33:08 +0530 [thread overview]
Message-ID: <1128fe70-41b7-4f68-8c90-34f291434b3a@linux.ibm.com> (raw)
In-Reply-To: <20260729033654.311541-9-coiby.xu@gmail.com>
On 29/07/26 09:06, Coiby Xu wrote:
> We should check the return codes so we can abort if keyring allocation
> or reading old memory fails.
>
> Note there is no need to refer a key add_key_to_keyring, so delete
> related code.
>
> Signed-off-by: Coiby Xu <coiby.xu@gmail.com>
> ---
> kernel/crash_dump_dm_crypt.c | 23 ++++++++++++++++-------
> 1 file changed, 16 insertions(+), 7 deletions(-)
>
> diff --git a/kernel/crash_dump_dm_crypt.c b/kernel/crash_dump_dm_crypt.c
> index 1f4549956824..b5b78656cf06 100644
> --- a/kernel/crash_dump_dm_crypt.c
> +++ b/kernel/crash_dump_dm_crypt.c
> @@ -65,7 +65,7 @@ static int add_key_to_keyring(struct dm_crypt_key *dm_key,
> key_ref_t keyring_ref)
> {
> key_ref_t key_ref;
> - int r;
> + int r = 0;
>
> /* create or update the requested key and add it to the target keyring */
> key_ref = key_create_or_update(keyring_ref, "user", dm_key->key_desc,
> @@ -73,8 +73,6 @@ static int add_key_to_keyring(struct dm_crypt_key *dm_key,
> KEY_USR_ALL, KEY_ALLOC_IN_QUOTA);
>
> if (!IS_ERR(key_ref)) {
> - r = key_ref_to_ptr(key_ref)->serial;
> - key_ref_put(key_ref);
> pr_debug("Success adding key %s", dm_key->key_desc);
> } else {
> r = PTR_ERR(key_ref);
> @@ -133,9 +131,14 @@ static int restore_dm_crypt_keys_to_thread_keyring(void)
> }
>
> addr = dm_crypt_keys_addr;
> - dm_crypt_keys_read((char *)&key_count, sizeof(key_count), &addr);
> + ret = dm_crypt_keys_read((char *)&key_count, sizeof(key_count), &addr);
> + if (ret < 0) {
> + pr_err("Failed to read the number of dm-crypt keys\n");
> + goto out;
> + }
> +
> if (key_count > KEY_NUM_MAX) {
> - pr_warn("Failed to read the number of dm-crypt keys\n");
> + pr_warn("Read %u dm-crypt keys (max=%u)\n", key_count, KEY_NUM_MAX);
> ret = -1;
> goto out;
> }
> @@ -150,12 +153,18 @@ static int restore_dm_crypt_keys_to_thread_keyring(void)
> goto out;
> }
>
> - dm_crypt_keys_read((char *)keys_header, keys_header_size, &addr);
> + ret = dm_crypt_keys_read((char *)keys_header, keys_header_size, &addr);
> + if (ret < 0) {
> + pr_err("Failed to read dm-crypt keys\n");
> + goto out;
> + }
>
> for (int i = 0; i < keys_header->total_keys; i++) {
> key = &keys_header->keys[i];
> pr_debug("Get key (size=%u)\n", key->key_size);
> - add_key_to_keyring(key, keyring_ref);
> + ret = add_key_to_keyring(key, keyring_ref);
> + if (ret)
> + break;
> }
>
> out:
Changes looks good to me. Feel free to add.
Reviewed-by: Sourabh Jain <sourabhjain@linux.ibm.com>
next prev parent reply other threads:[~2026-08-05 12:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260729033654.311541-1-coiby.xu@gmail.com>
2026-07-29 3:36 ` [PATCH v3 01/10] crash_dump: release keyring reference at the correct time Coiby Xu
2026-07-29 3:36 ` [PATCH v3 02/10] crash_dump: Fix potential double free and UAF of keys_header Coiby Xu
2026-07-29 3:36 ` [PATCH v3 03/10] crash_dump: Disallow writing to dm-crypt configfs during kexec_file_load syscall Coiby Xu
2026-08-05 10:30 ` Sourabh Jain
2026-08-06 5:20 ` Coiby Xu
2026-08-09 11:56 ` Sourabh Jain
2026-07-29 3:36 ` [PATCH v3 04/10] crash_dump: Read the number of dm-crypt keys from reserved memory Coiby Xu
2026-08-05 11:05 ` Sourabh Jain
2026-08-06 6:20 ` Coiby Xu
2026-08-09 12:26 ` Sourabh Jain
2026-07-29 3:36 ` [PATCH v3 05/10] crash_dump: Free temporary dm-crypt keys_header buffer in kdump kernel Coiby Xu
2026-08-05 11:20 ` Sourabh Jain
2026-07-29 3:36 ` [PATCH v3 06/10] crash_dump: Only use kexec_dprintk during the kexec_file_load syscall Coiby Xu
2026-08-05 11:36 ` Sourabh Jain
2026-08-06 5:27 ` Coiby Xu
2026-07-29 3:36 ` [PATCH v3 07/10] crash_dump: Improve readability of config_keys_restore_store Coiby Xu
2026-08-05 11:52 ` Sourabh Jain
2026-08-06 6:26 ` Coiby Xu
2026-07-29 3:36 ` [PATCH v3 08/10] crash_dump: Check the function return codes in restore_dm_crypt_keys_to_thread_keyring Coiby Xu
2026-08-05 12:03 ` Sourabh Jain [this message]
2026-07-29 3:36 ` [PATCH v3 09/10] crash_dump: Disallow configfs/crash_dm_crypt_key/reuse if crash hotplug supported Coiby Xu
2026-08-05 12:09 ` Sourabh Jain
2026-08-06 5:33 ` Coiby Xu
2026-08-09 12:06 ` Sourabh Jain
2026-07-29 3:36 ` [PATCH v3 10/10] Documentation: kdump: Add arm64 and ppc64le to encrypted dump target support list Coiby Xu
2026-08-05 12:10 ` Sourabh Jain
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=1128fe70-41b7-4f68-8c90-34f291434b3a@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=coiby.xu@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=ruirui.yang@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®