On Fri, 26 Jun 2020, Herbert Xu wrote: > 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. There is no hard reason for that. CRYPTO_NOLOAD is a "virtual" flag that could be only present in crypto algorithm requests and I thought that the intention was that the virtual flags go after real flags. If you don't want to change existing flags, there is no problem with that. Mikulas > Thanks, > -- > Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > Home Page: http://gondor.apana.org.au/~herbert/ > PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt >
