[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230523165503.GA864814@google.com>
Date: Tue, 23 May 2023 16:55:03 +0000
From: Eric Biggers <ebiggers@...nel.org>
To: meenakshi.aggarwal@....com
Cc: horia.geanta@....com, V.sethi@....com, pankaj.gupta@....com,
gaurav.jain@....com, herbert@...dor.apana.org.au,
davem@...emloft.net, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org, iuliana.prodan@....com
Subject: Re: [PATCH 0/5] Remove CRYPTO_ALG_ALLOCATES_MEMORY flag
On Tue, May 23, 2023 at 05:34:16PM +0200, meenakshi.aggarwal@....com wrote:
> CRYPTO_ALG_ALLOCATES_MEMORY flag is limited only to dm-crypt use-cases,
> which seems to be 4 entries maximum.
This isn't mentioned in the documentation for CRYPTO_ALG_ALLOCATES_MEMORY. So
it's not part of the contract of CRYPTO_ALG_ALLOCATES_MEMORY currently.
Please don't make this change without updating the documentation.
If you'd like to make this change, please update the documentation for
CRYPTO_ALG_ALLOCATES_MEMORY to mention this additional exception.
- Eric
Powered by blists - more mailing lists