public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Harald Freudenberger <freude@linux.ibm.com>
Cc: dengler@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
	linux-s390@vger.kernel.org, herbert@gondor.apana.org.au,
	ifranzki@linux.ibm.com, fcallies@linux.ibm.com
Subject: Re: [PATCH v7 07/25] s390/zcrypt: Introduce cprb mempool for ep11 misc functions
Date: Thu, 24 Apr 2025 08:58:38 +0200	[thread overview]
Message-ID: <20250424065838.7083Bd6-hca@linux.ibm.com> (raw)
In-Reply-To: <20250423101535.143137-8-freude@linux.ibm.com>

On Wed, Apr 23, 2025 at 12:15:16PM +0200, Harald Freudenberger wrote:
> Introduce a cprb mempool for the zcrypt ep11 misc functions
> (zcrypt_ep11misc.*) do some preparation rework to support
> a do-not-allocate path through some zcrypt ep11 misc functions.
> 
> The mempool is controlled by the zcrypt module parameter
> "mempool_threshold" which shall control the minimal amount
> of memory items for CCA and EP11.
> 
> The mempool shall support "mempool_threshold" requests/replies
> in parallel which means for EP11 to hold a send and receive
> buffer memory per request. Each of this cprb space items is
> limited to 8 KB. So by default the mempool consumes
>   5 * 2 * 8KB = 80KB
> 
> If the mempool is depleted upon one ep11 misc functions is
> called with the ZCRYPT_XFLAG_NOMEMALLOC xflag set, the function
> will fail with -ENOMEM and the caller is responsible for taking
> further actions.
> 
> This is only part of an rework to support a new xflag
> ZCRYPT_XFLAG_NOMEMALLOC but not yet complete.
> 
> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
> Reviewed-by: Holger Dengler <dengler@linux.ibm.com>
> ---
>  drivers/s390/crypto/zcrypt_api.c      |   6 ++
>  drivers/s390/crypto/zcrypt_ep11misc.c | 149 +++++++++++++++-----------
>  drivers/s390/crypto/zcrypt_ep11misc.h |   1 +
>  3 files changed, 95 insertions(+), 61 deletions(-)

clang says:

    CC [M]  drivers/s390/crypto/zcrypt_ep11misc.o
      drivers/s390/crypto/zcrypt_ep11misc.c:1041:6: warning: variable 'rep_pl_size' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized]
       1041 |         if (!req)
            |             ^~~~
      drivers/s390/crypto/zcrypt_ep11misc.c:1121:20: note: uninitialized use occurs here
       1121 |         free_cprbmem(rep, rep_pl_size, true, xflags);
            |                           ^~~~~~~~~~~
      drivers/s390/crypto/zcrypt_ep11misc.c:1041:2: note: remove the 'if' if its condition is always false
       1041 |         if (!req)
            |         ^~~~~~~~~
       1042 |                 goto out;
            |                 ~~~~~~~~
      drivers/s390/crypto/zcrypt_ep11misc.c:1028:33: note: initialize the variable 'rep_pl_size' to silence this warning
       1028 |         size_t req_pl_size, rep_pl_size;
            |                                        ^
            |                                         = 0
      1 warning generated.

> @@ -1095,9 +1117,8 @@ static int ep11_cryptsingle(u16 card, u16 domain,
>  	*outbufsize = n;
>  
>  out:
> -	kfree(req);
> -	kfree(rep);
> -	kfree(urb);
> +	free_cprbmem(req, req_pl_size, true, xflags);
> +	free_cprbmem(rep, rep_pl_size, true, xflags);
>  	return rc;
>  }

Which is this hunk.

In addition:

> @@ -1161,7 +1183,7 @@ static int _ep11_unwrapkey(u16 card, u16 domain,
>  	req_pl_size = sizeof(struct uw_req_pl) + (iv ? 16 : 0)
>  		+ ASN1TAGLEN(keksize) + ASN1TAGLEN(0)
>  		+ ASN1TAGLEN(pinblob_size) + ASN1TAGLEN(enckeysize);
> -	req = alloc_cprb(req_pl_size);
> +	req = alloc_cprbmem(req_pl_size, xflags);
>  	if (!req)
>  		goto out;
>  	req_pl = (struct uw_req_pl *)(((u8 *)req) + sizeof(*req));
> @@ -1197,22 +1219,19 @@ static int _ep11_unwrapkey(u16 card, u16 domain,
>  	p += asn1tag_write(p, 0x04, enckey, enckeysize);
>  
>  	/* reply cprb and payload */
> -	rep = alloc_cprb(sizeof(struct uw_rep_pl));
> +	rep = alloc_cprbmem(sizeof(struct uw_rep_pl), xflags);
>  	if (!rep)
>  		goto out;
>  	rep_pl = (struct uw_rep_pl *)(((u8 *)rep) + sizeof(*rep));
>  
>  	/* urb and target */
> -	urb = kmalloc(sizeof(*urb), GFP_KERNEL);
> -	if (!urb)
> -		goto out;
>  	target.ap_id = card;
>  	target.dom_id = domain;
> -	prep_urb(urb, &target, 1,
> +	prep_urb(&urb, &target, 1,
>  		 req, sizeof(*req) + req_pl_size,
>  		 rep, sizeof(*rep) + sizeof(*rep_pl));
>  
> -	rc = zcrypt_send_ep11_cprb(urb, 0);
> +	rc = zcrypt_send_ep11_cprb(&urb, xflags);
>  	if (rc) {
>  		ZCRYPT_DBF_ERR("%s zcrypt_send_ep11_cprb(card=%d dom=%d) failed, rc=%d\n",
>  			       __func__, (int)card, (int)domain, rc);
> @@ -1245,9 +1264,8 @@ static int _ep11_unwrapkey(u16 card, u16 domain,
>  	*keybufsize = rep_pl->data_len;
>  
>  out:
> -	kfree(req);
> -	kfree(rep);
> -	kfree(urb);
> +	free_cprbmem(req, req_pl_size, true, xflags);

This would lead to a memset() with destination address 0 if alloc_cprbmem()
fails.

> @@ -1319,15 +1337,16 @@ static int _ep11_wrapkey(u16 card, u16 domain,
>  	} __packed * rep_pl;
>  	struct ep11_cprb *req = NULL, *rep = NULL;
>  	struct ep11_target_dev target;
> -	struct ep11_urb *urb = NULL;
> +	struct ep11_urb urb;
>  	size_t req_pl_size;
>  	int api, rc = -ENOMEM;
>  	u8 *p;
> +	const u32 xflags = 0;
>  
>  	/* request cprb and payload */
>  	req_pl_size = sizeof(struct wk_req_pl) + (iv ? 16 : 0)
>  		+ ASN1TAGLEN(keysize) + 4;
> -	req = alloc_cprb(req_pl_size);
> +	req = alloc_cprbmem(req_pl_size, xflags);
>  	if (!req)
>  		goto out;
...
> @@ -1405,9 +1421,8 @@ static int _ep11_wrapkey(u16 card, u16 domain,
>  	*datasize = rep_pl->data_len;
>  
>  out:
> -	kfree(req);
> -	kfree(rep);
> -	kfree(urb);
> +	free_cprbmem(req, req_pl_size, true, xflags);

Same here.

Please check all error paths in all patches and resubmit.
I'm going to revert the whole series for now. Thanks!

  reply	other threads:[~2025-04-24  6:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 10:15 [PATCH v7 00/25] AP bus/zcrypt/pkey/paes no-mem-alloc patches Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 01/25] s390/ap: Move response_type struct into ap_msg struct Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 02/25] s390/ap/zcrypt: Rework AP message buffer allocation Harald Freudenberger
2025-04-24  6:45   ` Heiko Carstens
2025-04-23 10:15 ` [PATCH v7 03/25] s390/ap: Introduce ap message buffer pool Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 04/25] s390/zcrypt: Avoid alloc and copy of ep11 targets if kernelspace cprb Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 05/25] s390/ap/zcrypt: New xflag parameter Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 06/25] s390/zcrypt: Introduce cprb mempool for cca misc functions Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 07/25] s390/zcrypt: Introduce cprb mempool for ep11 " Harald Freudenberger
2025-04-24  6:58   ` Heiko Carstens [this message]
2025-04-23 10:15 ` [PATCH v7 08/25] s390/zcrypt: Rework zcrypt function zcrypt_device_status_mask_ext Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 09/25] s390/zcrypt: Introduce pre-allocated device status array for cca misc Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 10/25] s390/zcrypt: Introduce pre-allocated device status array for ep11 misc Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 11/25] s390/zcrypt: Remove unused functions from cca misc Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 12/25] s390/zcrypt: Remove CCA and EP11 card and domain info caches Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 13/25] s390/zcrypt: Rework cca findcard() implementation and callers Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 14/25] s390/zcrypt: Rework ep11 " Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 15/25] s390/zcrypt: Rework cca misc functions kmallocs to use the cprb mempool Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 16/25] s390/zcrypt: Propagate xflags argument with cca_get_info() Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 17/25] s390/zcrypt: Locate ep11_domain_query_info onto the stack instead of kmalloc Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 18/25] s390/zcrypt: Rework ep11 misc functions to use cprb mempool Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 19/25] s390/pkey: Rework CCA pkey handler to use stack for small memory allocs Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 20/25] s390/pkey: Rework EP11 " Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 21/25] s390/uv: Rename find_secret() to uv_find_secret() and publish Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 22/25] s390/pkey: Use preallocated memory for retrieve of UV secret metadata Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 23/25] s390/uv: Remove uv_get_secret_metadata function Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 24/25] s390/pkey: Provide and pass xflags within pkey and zcrypt layers Harald Freudenberger
2025-04-23 10:15 ` [PATCH v7 25/25] s390/pkey/crypto: Introduce xflags param for pkey in-kernel API Harald Freudenberger
2025-04-23 10:40 ` [PATCH v7 00/25] AP bus/zcrypt/pkey/paes no-mem-alloc patches Heiko Carstens
2025-04-23 15:07   ` Harald Freudenberger
2025-04-23 15:15     ` Heiko Carstens

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=20250424065838.7083Bd6-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=dengler@linux.ibm.com \
    --cc=fcallies@linux.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=ifranzki@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    /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