From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Gonglei <arei.gonglei@huawei.com>,
Jason Wang <jasowang@redhat.com>,
zhenwei pi <pizhenwei@bytedance.com>,
lei he <helei.sig11@bytedance.com>,
virtualization@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH -next] crypto: virtio - Select new dependencies
Date: Tue, 8 Mar 2022 16:12:42 -0500 [thread overview]
Message-ID: <20220308161153-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220308205309.2192502-1-nathan@kernel.org>
On Tue, Mar 08, 2022 at 01:53:09PM -0700, Nathan Chancellor wrote:
> With ARCH=riscv defconfig, there are errors at link time:
>
> virtio_crypto_akcipher_algs.c:(.text+0x3ea): undefined reference to `mpi_free'
> virtio_crypto_akcipher_algs.c:(.text+0x48a): undefined reference to `rsa_parse_priv_key'
> virtio_crypto_akcipher_algs.c:(.text+0x4bc): undefined reference to `rsa_parse_pub_key'
> virtio_crypto_akcipher_algs.c:(.text+0x4d0): undefined reference to `mpi_read_raw_data'
> virtio_crypto_akcipher_algs.c:(.text+0x960): undefined reference to `crypto_register_akcipher'
> virtio_crypto_akcipher_algs.c:(.text+0xa3a): undefined reference to `crypto_unregister_akcipher'
>
> The virtio crypto driver started making use of certain libraries and
> algorithms without selecting them. Do so to fix these errors.
>
> Fixes: 8a75f36b5d7a ("virtio-crypto: implement RSA algorithm")
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Thanks! I'll squash this into the original commit so we don't
have a broken commit during bisect.
zhenwei pi, ack pls?
> ---
> drivers/crypto/virtio/Kconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/crypto/virtio/Kconfig b/drivers/crypto/virtio/Kconfig
> index b894e3a8be4f..5f8915f4a9ff 100644
> --- a/drivers/crypto/virtio/Kconfig
> +++ b/drivers/crypto/virtio/Kconfig
> @@ -3,8 +3,11 @@ config CRYPTO_DEV_VIRTIO
> tristate "VirtIO crypto driver"
> depends on VIRTIO
> select CRYPTO_AEAD
> + select CRYPTO_AKCIPHER2
> select CRYPTO_SKCIPHER
> select CRYPTO_ENGINE
> + select CRYPTO_RSA
> + select MPILIB
> help
> This driver provides support for virtio crypto device. If you
> choose 'M' here, this module will be called virtio_crypto.
>
> base-commit: c5f633abfd09491ae7ecbc7fcfca08332ad00a8b
> --
> 2.35.1
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: lei he <helei.sig11@bytedance.com>,
patches@lists.linux.dev, zhenwei pi <pizhenwei@bytedance.com>,
virtualization@lists.linux-foundation.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH -next] crypto: virtio - Select new dependencies
Date: Tue, 8 Mar 2022 16:12:42 -0500 [thread overview]
Message-ID: <20220308161153-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220308205309.2192502-1-nathan@kernel.org>
On Tue, Mar 08, 2022 at 01:53:09PM -0700, Nathan Chancellor wrote:
> With ARCH=riscv defconfig, there are errors at link time:
>
> virtio_crypto_akcipher_algs.c:(.text+0x3ea): undefined reference to `mpi_free'
> virtio_crypto_akcipher_algs.c:(.text+0x48a): undefined reference to `rsa_parse_priv_key'
> virtio_crypto_akcipher_algs.c:(.text+0x4bc): undefined reference to `rsa_parse_pub_key'
> virtio_crypto_akcipher_algs.c:(.text+0x4d0): undefined reference to `mpi_read_raw_data'
> virtio_crypto_akcipher_algs.c:(.text+0x960): undefined reference to `crypto_register_akcipher'
> virtio_crypto_akcipher_algs.c:(.text+0xa3a): undefined reference to `crypto_unregister_akcipher'
>
> The virtio crypto driver started making use of certain libraries and
> algorithms without selecting them. Do so to fix these errors.
>
> Fixes: 8a75f36b5d7a ("virtio-crypto: implement RSA algorithm")
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Thanks! I'll squash this into the original commit so we don't
have a broken commit during bisect.
zhenwei pi, ack pls?
> ---
> drivers/crypto/virtio/Kconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/crypto/virtio/Kconfig b/drivers/crypto/virtio/Kconfig
> index b894e3a8be4f..5f8915f4a9ff 100644
> --- a/drivers/crypto/virtio/Kconfig
> +++ b/drivers/crypto/virtio/Kconfig
> @@ -3,8 +3,11 @@ config CRYPTO_DEV_VIRTIO
> tristate "VirtIO crypto driver"
> depends on VIRTIO
> select CRYPTO_AEAD
> + select CRYPTO_AKCIPHER2
> select CRYPTO_SKCIPHER
> select CRYPTO_ENGINE
> + select CRYPTO_RSA
> + select MPILIB
> help
> This driver provides support for virtio crypto device. If you
> choose 'M' here, this module will be called virtio_crypto.
>
> base-commit: c5f633abfd09491ae7ecbc7fcfca08332ad00a8b
> --
> 2.35.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-03-08 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 20:53 [PATCH -next] crypto: virtio - Select new dependencies Nathan Chancellor
2022-03-08 21:12 ` Michael S. Tsirkin [this message]
2022-03-08 21:12 ` Michael S. Tsirkin
2022-03-09 1:55 ` zhenwei pi
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=20220308161153-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=helei.sig11@bytedance.com \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=patches@lists.linux.dev \
--cc=pizhenwei@bytedance.com \
--cc=virtualization@lists.linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.