From: Eric Biggers <ebiggers@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Mike Snitzer <msnitzer@redhat.com>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
linux-crypto@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Milan Broz <mbroz@redhat.com>
Subject: Re: [dm-devel] [PATCH 3/4] crypto: set the flag CRYPTO_ALG_ALLOCATES_MEMORY
Date: Tue, 16 Jun 2020 10:43:40 -0700 [thread overview]
Message-ID: <20200616174340.GC207319@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.02.2006161102020.28052@file01.intranet.prod.int.rdu2.redhat.com>
On Tue, Jun 16, 2020 at 11:02:20AM -0400, Mikulas Patocka wrote:
> Set the flag CRYPTO_ALG_ALLOCATES_MEMORY in the crypto drivers that
> allocate memory.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>
> ---
> drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c | 8 +-
> drivers/crypto/allwinner/sun8i-ss/sun8i-ss-core.c | 8 +-
> drivers/crypto/amlogic/amlogic-gxl-core.c | 4 -
> drivers/crypto/axis/artpec6_crypto.c | 20 +++--
> drivers/crypto/bcm/cipher.c | 38 +++++-----
> drivers/crypto/caam/caamalg.c | 4 -
> drivers/crypto/caam/caamalg_qi.c | 4 -
> drivers/crypto/caam/caamalg_qi2.c | 6 -
> drivers/crypto/caam/caamhash.c | 2
> drivers/crypto/cavium/cpt/cptvf_algs.c | 12 +--
> drivers/crypto/cavium/nitrox/nitrox_aead.c | 4 -
> drivers/crypto/cavium/nitrox/nitrox_skcipher.c | 16 ++--
> drivers/crypto/ccp/ccp-crypto-aes-cmac.c | 1
> drivers/crypto/ccp/ccp-crypto-aes-galois.c | 1
> drivers/crypto/ccp/ccp-crypto-aes-xts.c | 1
> drivers/crypto/ccp/ccp-crypto-aes.c | 2
> drivers/crypto/ccp/ccp-crypto-des3.c | 1
> drivers/crypto/ccp/ccp-crypto-sha.c | 1
> drivers/crypto/chelsio/chcr_algo.c | 6 -
> drivers/crypto/hisilicon/sec/sec_algs.c | 16 ++--
> drivers/crypto/hisilicon/sec2/sec_crypto.c | 4 -
> drivers/crypto/inside-secure/safexcel_cipher.c | 47 +++++++++++++
> drivers/crypto/inside-secure/safexcel_hash.c | 18 +++++
> drivers/crypto/ixp4xx_crypto.c | 6 +
> drivers/crypto/marvell/cesa/cipher.c | 12 +--
> drivers/crypto/marvell/cesa/hash.c | 6 +
> drivers/crypto/marvell/octeontx/otx_cptvf_algs.c | 30 ++++----
> drivers/crypto/n2_core.c | 2
> drivers/crypto/picoxcell_crypto.c | 17 ++++
> drivers/crypto/qat/qat_common/qat_algs.c | 12 +--
> drivers/crypto/qce/sha.c | 2
> drivers/crypto/qce/skcipher.c | 1
> drivers/crypto/talitos.c | 78 +++++++++++-----------
> drivers/crypto/virtio/virtio_crypto_algs.c | 2
> drivers/crypto/xilinx/zynqmp-aes-gcm.c | 1
> 35 files changed, 248 insertions(+), 145 deletions(-)
It would be helpful if there was a pointer to where the memory allocation
happens in each driver.
- Eric
next prev parent reply other threads:[~2020-06-16 17:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 17:11 crypto API and GFP_ATOMIC Mikulas Patocka
2020-06-10 1:04 ` Herbert Xu
2020-06-10 12:02 ` Mikulas Patocka
2020-06-10 12:11 ` Herbert Xu
2020-06-16 15:01 ` Mikulas Patocka
2020-06-16 15:01 ` [PATCH 1/4] crypto: introduce CRYPTO_ALG_ALLOCATES_MEMORY Mikulas Patocka
2020-06-16 17:36 ` [dm-devel] " Eric Biggers
2020-06-17 15:08 ` Mikulas Patocka
2020-06-17 15:09 ` [PATCH 1/3] crypto: pass the flag CRYPTO_ALG_ALLOCATES_MEMORY Mikulas Patocka
2020-06-26 4:45 ` Herbert Xu
2020-06-26 15:17 ` Mikulas Patocka
2020-06-26 16:16 ` [PATCH 1/3 v2] crypto: introduce " Mikulas Patocka
2020-06-26 16:46 ` Eric Biggers
2020-06-26 17:00 ` [dm-devel] " Eric Biggers
2020-06-28 19:07 ` Mikulas Patocka
2020-06-28 19:50 ` Eric Biggers
2020-06-30 13:57 ` Mikulas Patocka
2020-06-28 20:00 ` Eric Biggers
2020-06-29 13:17 ` Mikulas Patocka
2020-06-30 13:45 ` Mikulas Patocka
2020-06-28 19:04 ` Mikulas Patocka
2020-06-28 19:46 ` Eric Biggers
2020-06-28 19:05 ` [PATCH 1/3 v3] " Mikulas Patocka
2020-06-30 13:56 ` [PATCH 1/3 v4] " Mikulas Patocka
2020-06-30 16:35 ` [dm-devel] " Eric Biggers
2020-06-30 17:01 ` Mikulas Patocka
2020-06-30 17:02 ` [PATCH 1/3 v5] " Mikulas Patocka
2020-06-30 17:57 ` [dm-devel] [PATCH 1/3 v4] " Eric Biggers
2020-06-30 18:14 ` Mikulas Patocka
2020-06-30 18:15 ` [PATCH 1/3 v6] " Mikulas Patocka
2020-07-01 1:49 ` Herbert Xu
2020-06-17 15:10 ` [PATCH 2/3] crypto: set " Mikulas Patocka
2020-06-17 15:11 ` [PATCH 3/3] dm-crypt: don't use drivers that have CRYPTO_ALG_ALLOCATES_MEMORY Mikulas Patocka
2020-06-16 15:01 ` [PATCH 2/4] crypto: pass the flag CRYPTO_ALG_ALLOCATES_MEMORY Mikulas Patocka
2020-06-16 17:42 ` [dm-devel] " Eric Biggers
2020-06-16 15:02 ` [PATCH 3/4] crypto: set " Mikulas Patocka
2020-06-16 17:43 ` Eric Biggers [this message]
2020-06-16 15:02 ` [PATCH 4/4] crypto: fix the drivers that don't respect CRYPTO_TFM_REQ_MAY_SLEEP Mikulas Patocka
2020-06-16 17:50 ` [dm-devel] " Eric Biggers
2020-06-16 18:18 ` Mikulas Patocka
2020-06-16 18:23 ` Eric Biggers
2020-06-17 13:46 ` Mikulas Patocka
2020-06-17 13:48 ` [PATCH 1/2] cpt-crypto: don't sleep of CRYPTO_TFM_REQ_MAY_SLEEP was not specified Mikulas Patocka
2020-06-26 6:07 ` Herbert Xu
2020-06-17 13:49 ` [PATCH 2/2] hisilicon-crypto: " Mikulas Patocka
2020-06-17 14:11 ` [dm-devel] " Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200616174340.GC207319@gmail.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=mpatocka@redhat.com \
--cc=msnitzer@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).