Hi Eric, We are not updating the functioning of CRYPTO_ALG_ALLOCATES_MEMORY flag. We have introduced the changes in CAAM driver and this flag is no longer required for CAAM use-cases. I will update the description of my patches in next version. Thanks, Meenakshi > -----Original Message----- > From: Eric Biggers <ebiggers@xxxxxxxxxx> > Sent: Tuesday, May 23, 2023 10:25 PM > To: Meenakshi Aggarwal <meenakshi.aggarwal@xxxxxxx> > Cc: Horia Geanta <horia.geanta@xxxxxxx>; Varun Sethi <V.Sethi@xxxxxxx>; > Pankaj Gupta <pankaj.gupta@xxxxxxx>; Gaurav Jain <gaurav.jain@xxxxxxx>; > herbert@xxxxxxxxxxxxxxxxxxx; davem@xxxxxxxxxxxxx; linux- > crypto@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Iuliana Prodan > <iuliana.prodan@xxxxxxx> > Subject: Re: [PATCH 0/5] Remove CRYPTO_ALG_ALLOCATES_MEMORY flag > > On Tue, May 23, 2023 at 05:34:16PM +0200, meenakshi.aggarwal@xxxxxxx > 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
