public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] crash_dump: Fix typo in function name read_key_from_user_keying
@ 2026-02-27 23:04 Thorsten Blum
  2026-03-02  3:28 ` Baoquan He
  0 siblings, 1 reply; 2+ messages in thread
From: Thorsten Blum @ 2026-02-27 23:04 UTC (permalink / raw)
  To: Andrew Morton, Baoquan He, Vivek Goyal, Dave Young
  Cc: Thorsten Blum, kexec, linux-kernel

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)
 {
 	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


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] crash_dump: Fix typo in function name read_key_from_user_keying
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Baoquan He @ 2026-03-02  3:28 UTC (permalink / raw)
  To: Thorsten Blum; +Cc: Andrew Morton, Vivek Goyal, Dave Young, kexec, linux-kernel

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
> 
> 


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-03-02  3:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox