public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crash_dump: Fix typo in function name read_key_from_user_keying
Date: Mon, 2 Mar 2026 11:28:35 +0800	[thread overview]
Message-ID: <aaUD40DNfYVup9rN@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20260227230422.859423-1-thorsten.blum@linux.dev>

On 02/28/26 at 12:04am, Thorsten Blum wrote:
> The function read_key_from_user_keying() is missing an 'r' in its name.
> Fix the typo by renaming it to read_key_from_user_keyring().
> 
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
>  kernel/crash_dump_dm_crypt.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/crash_dump_dm_crypt.c b/kernel/crash_dump_dm_crypt.c
> index 27a144920562..dcb69e96c6ff 100644
> --- a/kernel/crash_dump_dm_crypt.c
> +++ b/kernel/crash_dump_dm_crypt.c
> @@ -139,7 +139,7 @@ static int restore_dm_crypt_keys_to_thread_keyring(void)
>  	return 0;
>  }
>  
> -static int read_key_from_user_keying(struct dm_crypt_key *dm_key)
> +static int read_key_from_user_keyring(struct dm_crypt_key *dm_key)

Good catch.

Acked-by: Baoquan He <bhe@redhat.com>

By the way, it's better to wrap these cleanup/fix patches into a
patchset for easier reviewing and merging when you are exploring code
flow of one feature/component. Anyway, thanks.

>  {
>  	const struct user_key_payload *ukp;
>  	struct key *key;
> @@ -387,7 +387,7 @@ static int build_keys_header(void)
>  
>  		strscpy(keys_header->keys[i].key_desc, key->description,
>  			KEY_DESC_MAX_LEN);
> -		r = read_key_from_user_keying(&keys_header->keys[i]);
> +		r = read_key_from_user_keyring(&keys_header->keys[i]);
>  		if (r != 0) {
>  			kexec_dprintk("Failed to read key %s\n",
>  				      keys_header->keys[i].key_desc);
> -- 
> Thorsten Blum <thorsten.blum@linux.dev>
> GPG: 1D60 735E 8AEF 3BE4 73B6  9D84 7336 78FD 8DFE EAD4
> 
> 


      reply	other threads:[~2026-03-02  3:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 23:04 [PATCH] crash_dump: Fix typo in function name read_key_from_user_keying Thorsten Blum
2026-03-02  3:28 ` Baoquan He [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=aaUD40DNfYVup9rN@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thorsten.blum@linux.dev \
    --cc=vgoyal@redhat.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