From: Randy Dunlap <rdunlap@infradead.org>
To: Sven Schnelle <svens@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-next@vger.kernel.org,
Anastasia Eskova <anastasia.eskova@ibm.com>
Subject: Re: [PATCH] s390/certstore: select CRYPTO_LIB_SHA256
Date: Mon, 31 Jul 2023 19:16:03 -0700 [thread overview]
Message-ID: <57c5ba80-bc87-e76a-98f1-5f8043711b0a@infradead.org> (raw)
In-Reply-To: <20230728100430.1567328-1-svens@linux.ibm.com>
On 7/28/23 03:04, Sven Schnelle wrote:
> A build failure was reported when sha256() is not present:
>
> gcc-13.1.0-nolibc/s390-linux/bin/s390-linux-ld: arch/s390/kernel/cert_store.o: in function `check_certificate_hash':
> arch/s390/kernel/cert_store.c:267: undefined reference to `sha256'
>
> Therefore make CONFIG_CERT_STORE select CRYPTO_LIB_SHA256.
>
> Fixes: 8cf57d7217c3 ("s390: add support for user-defined certificates")
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Closes: https://lore.kernel.org/all/8ecb57fb-4560-bdfc-9e55-63e3b0937132@infradead.org/
> Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
Sorry for the delay.
Tested-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> arch/s390/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
> index d9d50a7a2016..18bf754e1fad 100644
> --- a/arch/s390/Kconfig
> +++ b/arch/s390/Kconfig
> @@ -516,6 +516,7 @@ config KEXEC_SIG
> config CERT_STORE
> bool "Get user certificates via DIAG320"
> depends on KEYS
> + select CRYPTO_LIB_SHA256
> help
> Enable this option if you want to access user-provided secure boot
> certificates via DIAG 0x320.
--
~Randy
prev parent reply other threads:[~2023-08-01 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:04 Sven Schnelle
2023-07-29 13:48 ` Heiko Carstens
2023-08-01 2:16 ` Randy Dunlap [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=57c5ba80-bc87-e76a-98f1-5f8043711b0a@infradead.org \
--to=rdunlap@infradead.org \
--cc=agordeev@linux.ibm.com \
--cc=anastasia.eskova@ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.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
all inboxes | Powered by JetHome®