* [PATCH] keys: remove __user annotation from function prototype
@ 2022-01-22 20:15 Randy Dunlap
2022-03-27 6:35 ` Randy Dunlap
0 siblings, 1 reply; 2+ messages in thread
From: Randy Dunlap @ 2022-01-22 20:15 UTC (permalink / raw)
To: linux-kernel
Cc: Randy Dunlap, Jann Horn, David Howells, Jarkko Sakkinen, keyrings
Remove a missed __user annotation from the prototype for
keyring_read(). This cures a sparse warning when it complains about
the difference in the prototype and the function definition.
security/keys/keyring.c:481:13: sparse: long static [signed] [toplevel] keyring_read( ... )
security/keys/keyring.c:81:13: sparse: long static [addressable] [signed] [toplevel] keyring_read( ... )
Fixes: 796e46f9e2cb ("keys: Remove outdated __user annotations").
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jann Horn <jannh@google.com>
Cc: David Howells <dhowells@redhat.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>
Cc: keyrings@vger.kernel.org
---
security/keys/keyring.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20220121.orig/security/keys/keyring.c
+++ linux-next-20220121/security/keys/keyring.c
@@ -79,7 +79,7 @@ static void keyring_revoke(struct key *k
static void keyring_destroy(struct key *keyring);
static void keyring_describe(const struct key *keyring, struct seq_file *m);
static long keyring_read(const struct key *keyring,
- char __user *buffer, size_t buflen);
+ char *buffer, size_t buflen);
struct key_type key_type_keyring = {
.name = "keyring",
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [PATCH] keys: remove __user annotation from function prototype
2022-01-22 20:15 [PATCH] keys: remove __user annotation from function prototype Randy Dunlap
@ 2022-03-27 6:35 ` Randy Dunlap
0 siblings, 0 replies; 2+ messages in thread
From: Randy Dunlap @ 2022-03-27 6:35 UTC (permalink / raw)
To: linux-kernel; +Cc: Jann Horn, David Howells, Jarkko Sakkinen, keyrings
ping.
On 1/22/22 12:15, Randy Dunlap wrote:
> Remove a missed __user annotation from the prototype for
> keyring_read(). This cures a sparse warning when it complains about
> the difference in the prototype and the function definition.
>
> security/keys/keyring.c:481:13: sparse: long static [signed] [toplevel] keyring_read( ... )
> security/keys/keyring.c:81:13: sparse: long static [addressable] [signed] [toplevel] keyring_read( ... )
>
> Fixes: 796e46f9e2cb ("keys: Remove outdated __user annotations").
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jann Horn <jannh@google.com>
> Cc: David Howells <dhowells@redhat.com>
> Cc: Jarkko Sakkinen <jarkko@kernel.org>
> Cc: keyrings@vger.kernel.org
> ---
> security/keys/keyring.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20220121.orig/security/keys/keyring.c
> +++ linux-next-20220121/security/keys/keyring.c
> @@ -79,7 +79,7 @@ static void keyring_revoke(struct key *k
> static void keyring_destroy(struct key *keyring);
> static void keyring_describe(const struct key *keyring, struct seq_file *m);
> static long keyring_read(const struct key *keyring,
> - char __user *buffer, size_t buflen);
> + char *buffer, size_t buflen);
>
> struct key_type key_type_keyring = {
> .name = "keyring",
--
~Randy
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-03-27 6:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-22 20:15 [PATCH] keys: remove __user annotation from function prototype Randy Dunlap
2022-03-27 6:35 ` Randy Dunlap
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®