[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200628200022.GE11197@sol.localdomain>
Date: Sun, 28 Jun 2020 13:00:22 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Mikulas Patocka <mpatocka@...hat.com>
Cc: Mike Snitzer <msnitzer@...hat.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Zaibo Xu <xuzaibo@...wei.com>, linux-kernel@...r.kernel.org,
Wei Xu <xuwei5@...ilicon.com>, dm-devel@...hat.com,
George Cherian <gcherian@...vell.com>,
linux-crypto@...r.kernel.org,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
"David S. Miller" <davem@...emloft.net>,
Milan Broz <mbroz@...hat.com>
Subject: Re: [dm-devel] [PATCH 1/3 v2] crypto: introduce the flag
CRYPTO_ALG_ALLOCATES_MEMORY
On Sun, Jun 28, 2020 at 03:07:49PM -0400, Mikulas Patocka wrote:
> >
> > cryptd_create_skcipher(), cryptd_create_hash(), cryptd_create_aead(), and
> > crypto_rfc4309_create() are also missing setting the mask.
> >
> > pcrypt_create_aead() is missing both setting the mask and inheriting the flags.
>
> I added CRYPTO_ALG_ALLOCATES_MEMORY there.
I don't see where the cryptd request processing functions allocate memory.
It seems that cryptd should just inherit the flag, like most other templates.
Likewise for pcrypt.
And also likewise for rfc4309.
Where are you seeing the memory allocations that would require
CRYPTO_ALG_ALLOCATES_MEMORY to always be enabled for these?
- Eric
Powered by blists - more mailing lists