[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200626044534.GA2870@gondor.apana.org.au>
Date: Fri, 26 Jun 2020 14:45:34 +1000
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Mikulas Patocka <mpatocka@...hat.com>
Cc: Eric Biggers <ebiggers@...nel.org>,
Mike Snitzer <msnitzer@...hat.com>,
linux-kernel@...r.kernel.org, dm-devel@...hat.com,
linux-crypto@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Milan Broz <mbroz@...hat.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
George Cherian <gcherian@...vell.com>,
Wei Xu <xuwei5@...ilicon.com>, Zaibo Xu <xuzaibo@...wei.com>
Subject: Re: [PATCH 1/3] crypto: pass the flag CRYPTO_ALG_ALLOCATES_MEMORY
On Wed, Jun 17, 2020 at 11:09:28AM -0400, Mikulas Patocka wrote:
>
> Index: linux-2.6/include/linux/crypto.h
> ===================================================================
> --- linux-2.6.orig/include/linux/crypto.h
> +++ linux-2.6/include/linux/crypto.h
> @@ -97,9 +97,18 @@
> #define CRYPTO_ALG_OPTIONAL_KEY 0x00004000
>
> /*
> + * The driver may allocate memory during request processing, so it shouldn't be
> + * used in cases where memory allocation failures aren't acceptable, such as
> + * during block device encryption.
> + */
> +#define CRYPTO_ALG_ALLOCATES_MEMORY 0x00008000
> +
> +/*
> * Don't trigger module loading
> */
> -#define CRYPTO_NOLOAD 0x00008000
> +#define CRYPTO_NOLOAD 0x00010000
> +
> +#define CRYPTO_ALG_INHERITED_FLAGS (CRYPTO_ALG_ASYNC | CRYPTO_ALG_ALLOCATES_MEMORY)
Any reason why you need to renumber NOLOAD? If not please keep
the existing values.
Thanks,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists