From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: <cgzones@googlemail.com>
Cc: "David Howells" <dhowells@redhat.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Eric Snowberg" <eric.snowberg@oracle.com>,
<keyrings@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<llvm@lists.linux.dev>
Subject: Re: [PATCH] keys: drop shadowing dead prototype
Date: Sat, 30 Nov 2024 04:31:25 +0200 [thread overview]
Message-ID: <D5Z5SKSAX8UT.2NXLQ5HZNP617@kernel.org> (raw)
In-Reply-To: <20241125110342.49015-1-cgoettsche@seltendoof.de>
On Mon Nov 25, 2024 at 1:03 PM EET, Christian Göttsche wrote:
> From: Christian Göttsche <cgzones@googlemail.com>
>
> The global variable pkcs7 does not exist.
> Drop the variable declaration, but keep the struct prototype needed for
> is_key_on_revocation_list().
>
> Reported by clang:
>
> ./include/keys/system_keyring.h:104:67: warning: declaration shadows a variable in the global scope [-Wshadow]
> 104 | static inline int is_key_on_revocation_list(struct pkcs7_message *pkcs7)
> | ^
> ./include/keys/system_keyring.h:76:30: note: previous declaration is here
> 76 | extern struct pkcs7_message *pkcs7;
> | ^
>
> Fixes: 56c5812623f9 ("certs: Add EFI_CERT_X509_GUID support for dbx entries")
> Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
> ---
> include/keys/system_keyring.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/keys/system_keyring.h b/include/keys/system_keyring.h
> index 8365adf842ef..a6c2897bcc63 100644
> --- a/include/keys/system_keyring.h
> +++ b/include/keys/system_keyring.h
> @@ -73,7 +73,6 @@ static inline void __init set_machine_trusted_keys(struct key *keyring)
> }
> #endif
>
> -extern struct pkcs7_message *pkcs7;
> #ifdef CONFIG_SYSTEM_BLACKLIST_KEYRING
> extern int mark_hash_blacklisted(const u8 *hash, size_t hash_len,
> enum blacklist_hash_type hash_type);
> @@ -93,6 +92,7 @@ static inline int is_binary_blacklisted(const u8 *hash, size_t hash_len)
> }
> #endif
>
> +struct pkcs7_message;
> #ifdef CONFIG_SYSTEM_REVOCATION_LIST
> extern int add_key_to_revocation_list(const char *data, size_t size);
> extern int is_key_on_revocation_list(struct pkcs7_message *pkcs7);
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
prev parent reply other threads:[~2024-11-30 2:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 11:03 Christian Göttsche
2024-11-30 2:31 ` Jarkko Sakkinen [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=D5Z5SKSAX8UT.2NXLQ5HZNP617@kernel.org \
--to=jarkko@kernel.org \
--cc=cgzones@googlemail.com \
--cc=dhowells@redhat.com \
--cc=eric.snowberg@oracle.com \
--cc=justinstitt@google.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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
Powered by JetHome