From: Harald Freudenberger <freude@linux.ibm.com>
To: Holger Dengler <dengler@linux.ibm.com>
Cc: ifranzki@linux.ibm.com, fcallies@linux.ibm.com,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
linux-s390@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH v2 07/20] s390/zcrypt: Rework zcrypt function zcrypt_device_status_mask_ext
Date: Tue, 25 Mar 2025 10:24:25 +0100 [thread overview]
Message-ID: <4d82c1e8fe9cf60eb7393a0e91c71033@linux.ibm.com> (raw)
In-Reply-To: <64bab2ed-4302-45bf-b831-009c5b2d34e1@linux.ibm.com>
On 2025-03-19 12:03, Holger Dengler wrote:
> On 04/03/2025 18:21, Harald Freudenberger wrote:
>> Rework the existing function zcrypt_device_status_mask_ext():
>> * Add two new parameters to provide upper limits for
>> cards and queues. The existing implementation needed an
>> array of 256 * 256 * 4 = 256 KB which is really huge. The
>> reworked function is more flexible in the sense that the
>> caller can decide the upper limit for cards and domains to
>> be stored into the status array. So for example a caller may
>> decide to only query for cards 0...127 and queues 0...127
>> and thus only an array of size 128 * 128 * 4 = 64 KB is needed.
>> * Instead of void the reworked function now returns an int.
>> The currently only way to have the function return != 0
>> is by providing card or domains limits beyond 256.
>
> I would prefer to stay with a void function and limit the card and
> domain values to the current maximum. Details below.
>
>>
>> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
>> ---
>> drivers/s390/crypto/zcrypt_api.c | 20 +++++++++++++++-----
>> drivers/s390/crypto/zcrypt_api.h | 3 ++-
>> drivers/s390/crypto/zcrypt_ccamisc.c | 22 +++++++++++++++++-----
>> drivers/s390/crypto/zcrypt_ep11misc.c | 14 ++++++++++----
>> 4 files changed, 44 insertions(+), 15 deletions(-)
>>
>> diff --git a/drivers/s390/crypto/zcrypt_api.c
>> b/drivers/s390/crypto/zcrypt_api.c
>> index 62cc05881b13..bd2738e3792a 100644
>> --- a/drivers/s390/crypto/zcrypt_api.c
>> +++ b/drivers/s390/crypto/zcrypt_api.c
>> @@ -1317,19 +1317,25 @@ static void zcrypt_device_status_mask(struct
>> zcrypt_device_status *devstatus)
>> spin_unlock(&zcrypt_list_lock);
>> }
>>
>> -void zcrypt_device_status_mask_ext(struct zcrypt_device_status_ext
>> *devstatus)
>> +int zcrypt_device_status_mask_ext(struct zcrypt_device_status_ext
>> *devstatus,
>> + int maxcard, int maxqueue)
>
> Keep void and ...
>
>> {
>> struct zcrypt_card *zc;
>> struct zcrypt_queue *zq;
>> struct zcrypt_device_status_ext *stat;
>> int card, queue;
>>
>> + if (maxcard > MAX_ZDEV_CARDIDS_EXT || maxqueue >
>> MAX_ZDEV_DOMAINS_EXT)
>> + return -EINVAL;
>> +
>
> ... limit maxcard/maxqueue to the maximum supported values. In my
> opinion, it does not make any sense to call this function with higher
> values than the maximum.
>
> maxcard = MIN(maxcard, MAX_ZDEV_CARDIDS_EXT);
> maxqueue = MIN(maxqueue, MAX_ZDEV_DOMAINS_EXT);
>
> As a side effect, it keeps the caller code much simpler.
>
>> spin_lock(&zcrypt_list_lock);
>> for_each_zcrypt_card(zc) {
>> for_each_zcrypt_queue(zq, zc) {
>> card = AP_QID_CARD(zq->queue->qid);
>> queue = AP_QID_QUEUE(zq->queue->qid);
>> - stat = &devstatus[card * AP_DOMAINS + queue];
>> + if (card >= maxcard || queue >= maxqueue)
>> + continue;
>> + stat = &devstatus[card * maxqueue + queue];
>> stat->hwtype = zc->card->ap_dev.device_type;
>> stat->functions = zc->card->hwinfo.fac >> 26;
>> stat->qid = zq->queue->qid;
> [...]
>> @@ -1635,9 +1643,11 @@ static long zcrypt_unlocked_ioctl(struct file
>> *filp, unsigned int cmd,
>> GFP_KERNEL);
>> if (!device_status)
>> return -ENOMEM;
>> - zcrypt_device_status_mask_ext(device_status);
>> - if (copy_to_user((char __user *)arg, device_status,
>> - total_size))
>> + rc = zcrypt_device_status_mask_ext(device_status,
>> + MAX_ZDEV_CARDIDS_EXT,
>> + MAX_ZDEV_DOMAINS_EXT);
>> + if (!rc && copy_to_user((char __user *)arg, device_status,
>> + total_size))
>
> With the change above, you can stay with the current error handling.
> Only the addition parameters for zcrypt_device_status_mask_ext() need
> to be added.
>
>> rc = -EFAULT;
>> kvfree(device_status);
>> return rc;
> [...]
Done as suggested - only I used typed min (min_t()) instead of MIN.
-> v3
next prev parent reply other threads:[~2025-03-25 9:24 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 17:20 [PATCH v2 00/20] AP bus/zcrypt/pkey/paes no-mem-alloc patches Harald Freudenberger
2025-03-04 17:20 ` [PATCH v2 01/20] s390/ap: Move response_type struct into ap_msg struct Harald Freudenberger
2025-03-17 9:38 ` Holger Dengler
2025-03-24 14:34 ` Harald Freudenberger
2025-03-04 17:20 ` [PATCH v2 02/20] s390/ap/zcrypt: Rework AP message buffer allocation Harald Freudenberger
2025-03-17 13:57 ` Holger Dengler
2025-03-04 17:20 ` [PATCH v2 03/20] s390/ap: Introduce ap message buffer pool Harald Freudenberger
2025-03-17 16:14 ` Holger Dengler
2025-03-24 14:41 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 04/20] s390/ap/zcrypt: New xflag parameter and extension of the ap msg flags Harald Freudenberger
2025-03-18 12:16 ` Holger Dengler
2025-03-24 15:52 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 05/20] s390/zcrypt: Introduce cprb mempool for cca misc functions Harald Freudenberger
2025-03-18 14:16 ` Holger Dengler
2025-03-25 8:26 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 06/20] s390/zcrypt: Introduce cprb mempool for ep11 " Harald Freudenberger
2025-03-18 15:16 ` Holger Dengler
2025-03-25 8:36 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 07/20] s390/zcrypt: Rework zcrypt function zcrypt_device_status_mask_ext Harald Freudenberger
2025-03-19 11:03 ` Holger Dengler
2025-03-25 9:24 ` Harald Freudenberger [this message]
2025-03-04 17:21 ` [PATCH v2 08/20] s390/zcrypt: Introduce pre-allocated device status array for cca misc Harald Freudenberger
2025-03-19 14:31 ` Holger Dengler
2025-03-25 10:51 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 09/20] s390/zcrypt: Introduce pre-allocated device status array for ep11 misc Harald Freudenberger
2025-03-19 18:02 ` Holger Dengler
2025-03-25 11:09 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 10/20] s390/zcrypt/pkey: Rework cca findcard() implementation and callers Harald Freudenberger
2025-03-19 17:58 ` Holger Dengler
2025-03-25 13:02 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 11/20] s390/zcrypt/pkey: Rework ep11 " Harald Freudenberger
2025-03-20 8:30 ` Holger Dengler
2025-03-25 13:12 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 12/20] s390/zcrypt: Rework cca misc functions kmallocs to use the cprb mempool Harald Freudenberger
2025-03-20 9:31 ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 13/20] s390/zcrypt: Add small mempool for cca info list entries Harald Freudenberger
2025-03-20 14:34 ` Holger Dengler
2025-03-25 13:32 ` Harald Freudenberger
2025-03-20 16:05 ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 14/20] s390/zcrypt: Locate ep11_domain_query_info onto the stack instead of kmalloc Harald Freudenberger
2025-03-20 14:41 ` Holger Dengler
2025-03-25 14:04 ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 15/20] s390/zcrypt: Rework ep11 misc functions to use cprb mempool Harald Freudenberger
2025-03-20 15:18 ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 16/20] s390/zcrypt: Add small mempool for ep11 card info list entries Harald Freudenberger
2025-03-20 16:09 ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 17/20] s390/pkey: Rework CCA pkey handler to use stack for small memory allocs Harald Freudenberger
2025-03-21 9:05 ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 18/20] s390/pkey: Rework EP11 " Harald Freudenberger
2025-03-21 9:06 ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 19/20] s390/zcrypt/pkey: Provide and pass xflags within pkey and zcrypt layers Harald Freudenberger
2025-03-20 16:30 ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 20/20] s390/pkey/crypto: Introduce xflags param for pkey in-kernel API Harald Freudenberger
2025-03-20 16:34 ` Holger Dengler
2025-03-20 16:40 ` [PATCH v2 00/20] AP bus/zcrypt/pkey/paes no-mem-alloc patches Holger Dengler
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=4d82c1e8fe9cf60eb7393a0e91c71033@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=fcallies@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.