[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210125185829.GA2818@duo.ucw.cz>
Date: Mon, 25 Jan 2021 19:58:29 +0100
From: Pavel Machek <pavel@....cz>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Anthony Iliopoulos <ailiop@...e.com>,
Mike Snitzer <snitzer@...hat.com>,
Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 4.19 12/58] dm integrity: select CRYPTO_SKCIPHER
Hi!
> From: Anthony Iliopoulos <ailiop@...e.com>
>
> [ Upstream commit f7b347acb5f6c29d9229bb64893d8b6a2c7949fb ]
>
> The integrity target relies on skcipher for encryption/decryption, but
> certain kernel configurations may not enable CRYPTO_SKCIPHER, leading to
> compilation errors due to unresolved symbols. Explicitly select
> CRYPTO_SKCIPHER for DM_INTEGRITY, since it is unconditionally dependent
> on it.
There is no such config option in 4.19. This patch is not suitable
here.
grep -r CRYPTO_SKCIPHER .
./include/crypto/skcipher.h:#ifndef _CRYPTO_SKCIPHER_H
./include/crypto/skcipher.h:#define _CRYPTO_SKCIPHER_H
./include/crypto/skcipher.h:#endif /* _CRYPTO_SKCIPHER_H */
Best regards,
Pavel
> +++ b/drivers/md/Kconfig
> @@ -527,6 +527,7 @@ config DM_INTEGRITY
> select BLK_DEV_INTEGRITY
> select DM_BUFIO
> select CRYPTO
> + select CRYPTO_SKCIPHER
> select ASYNC_XOR
> ---help---
> This device-mapper target emulates a block device that has
--
http://www.livejournal.com/~pavelmachek
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists