From: Harald Freudenberger <freude@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>
Cc: dengler@linux.ibm.com, ifranzki@linux.ibm.com,
fcallies@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
frankja@linux.ibm.com, imbrenda@linux.ibm.com,
linux-s390@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH v4 21/24] s390/uv: Rename find_secret() to uv_find_secret() and publish
Date: Mon, 14 Apr 2025 17:15:35 +0200 [thread overview]
Message-ID: <34a5faeee685e97e80a53e00ec846af5@linux.ibm.com> (raw)
In-Reply-To: <20250414080825.19379-B-seiden@linux.ibm.com>
On 2025-04-14 10:08, Steffen Eiden wrote:
> On Wed, Apr 09, 2025 at 04:03:02PM +0200, Harald Freudenberger wrote:
>> Rename the internal UV function find_secret() to uv_find_secret()
>> and publish it as new UV API in-kernel function.
>>
>> The pkey uv handler may be called in a do-not-allocate memory
>> situation where sleeping is allowed but allocating memory which
>> may cause IO operations is not. For example when an encrypted
>> swap file is used and the encryption is done via UV retrievable
>> secrets with protected keys.
>>
>> The UV API function uv_get_secret_metadata() allocates memory
>> and then calls the find_secret() function. By exposing the
>> find_secret() function as a new UV API function uv_find_secret()
>> it is possible to retrieve UV secret meta data without any
>> memory allocations from the UV when the caller offers space
>> for one struct uv_secret_list.
>>
>> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
>
> With the documentation improved:
>
> Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
>
>> ---
>> arch/s390/include/asm/uv.h | 3 +++
>> arch/s390/kernel/uv.c | 12 ++++++++----
>> 2 files changed, 11 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/s390/include/asm/uv.h b/arch/s390/include/asm/uv.h
>> index b11f5b6d0bd1..8d7e00fa2bf0 100644
>> --- a/arch/s390/include/asm/uv.h
>> +++ b/arch/s390/include/asm/uv.h
>> @@ -616,6 +616,9 @@ static inline int uv_remove_shared(unsigned long
>> addr)
>> return share(addr, UVC_CMD_REMOVE_SHARED_ACCESS);
>> }
>>
>> +int uv_find_secret(const u8 secret_id[UV_SECRET_ID_LEN],
>> + struct uv_secret_list *list,
>> + struct uv_secret_list_item_hdr *secret);
>> int uv_get_secret_metadata(const u8 secret_id[UV_SECRET_ID_LEN],
>> struct uv_secret_list_item_hdr *secret);
>> int uv_retrieve_secret(u16 secret_idx, u8 *buf, size_t buf_size);
>> diff --git a/arch/s390/kernel/uv.c b/arch/s390/kernel/uv.c
>> index 9f05df2da2f7..4acbbdff568f 100644
>> --- a/arch/s390/kernel/uv.c
>> +++ b/arch/s390/kernel/uv.c
>> @@ -681,12 +681,15 @@ static int find_secret_in_page(const u8
>> secret_id[UV_SECRET_ID_LEN],
>>
>> /*
> This documentation string does not make sense for an exported function.
> Let's
> add documentation from the get_metadata function.
>
>> * Do the actual search for `uv_get_secret_metadata`.
> Change this to something like:
>
> Locate a secret in the list by its id.
>
>> + * @secret_id: search pattern.
>> + * @list: ephemeral buffer space
>> + * @secret: output data, containing the secret's metadata.
>> *
> Add:
> * Search for a secret with the given secret_id in the Ultravisor
> secret store.
>
>> * Context: might sleep.
>> */
>> -static int find_secret(const u8 secret_id[UV_SECRET_ID_LEN],
>> - struct uv_secret_list *list,
>> - struct uv_secret_list_item_hdr *secret)
>> +int uv_find_secret(const u8 secret_id[UV_SECRET_ID_LEN],
>> + struct uv_secret_list *list,
>> + struct uv_secret_list_item_hdr *secret)
>
> ...
Done as you suggested.
Thanks
next prev parent reply other threads:[~2025-04-14 15:15 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 14:02 [PATCH v4 00/24] AP bus/zcrypt/pkey/paes no-mem-alloc patches Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 01/24] s390/ap: Move response_type struct into ap_msg struct Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 02/24] s390/ap/zcrypt: Rework AP message buffer allocation Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 03/24] s390/ap: Introduce ap message buffer pool Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 04/24] s390/zcrypt: Avoid alloc and copy of ep11 targets if kernelspace cprb Harald Freudenberger
2025-04-09 16:19 ` Holger Dengler
2025-04-09 14:02 ` [PATCH v4 05/24] s390/ap/zcrypt: New xflag parameter Harald Freudenberger
2025-04-09 16:25 ` Holger Dengler
2025-04-09 14:02 ` [PATCH v4 06/24] s390/zcrypt: Introduce cprb mempool for cca misc functions Harald Freudenberger
2025-04-11 12:40 ` Holger Dengler
2025-04-14 14:17 ` Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 07/24] s390/zcrypt: Introduce cprb mempool for ep11 " Harald Freudenberger
2025-04-11 12:58 ` Holger Dengler
2025-04-14 14:21 ` Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 08/24] s390/zcrypt: Rework zcrypt function zcrypt_device_status_mask_ext Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 09/24] s390/zcrypt: Introduce pre-allocated device status array for cca misc Harald Freudenberger
2025-04-11 13:06 ` Holger Dengler
2025-04-09 14:02 ` [PATCH v4 10/24] s390/zcrypt: Introduce pre-allocated device status array for ep11 misc Harald Freudenberger
2025-04-11 13:08 ` Holger Dengler
2025-04-09 14:02 ` [PATCH v4 11/24] s390/zcrypt: Remove unused functions from cca misc Harald Freudenberger
2025-04-11 13:10 ` Holger Dengler
2025-04-09 14:02 ` [PATCH v4 12/24] s390/zcrypt: Remove CCA and EP11 card and domain info caches Harald Freudenberger
2025-04-11 13:25 ` Holger Dengler
2025-04-14 14:39 ` Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 13/24] s390/zcrypt/pkey: Rework cca findcard() implementation and callers Harald Freudenberger
2025-04-11 14:16 ` Holger Dengler
2025-04-14 14:41 ` Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 14/24] s390/zcrypt/pkey: Rework ep11 " Harald Freudenberger
2025-04-11 14:18 ` Holger Dengler
2025-04-14 14:42 ` Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 15/24] s390/zcrypt: Rework cca misc functions kmallocs to use the cprb mempool Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 16/24] s390/zcrypt: Propagate xflags argument with cca_get_info() Harald Freudenberger
2025-04-11 14:25 ` Holger Dengler
2025-04-14 14:48 ` Harald Freudenberger
2025-04-14 15:04 ` Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 17/24] s390/zcrypt: Locate ep11_domain_query_info onto the stack instead of kmalloc Harald Freudenberger
2025-04-09 14:02 ` [PATCH v4 18/24] s390/zcrypt: Rework ep11 misc functions to use cprb mempool Harald Freudenberger
2025-04-09 14:03 ` [PATCH v4 19/24] s390/pkey: Rework CCA pkey handler to use stack for small memory allocs Harald Freudenberger
2025-04-09 14:03 ` [PATCH v4 20/24] s390/pkey: Rework EP11 " Harald Freudenberger
2025-04-09 14:03 ` [PATCH v4 21/24] s390/uv: Rename find_secret() to uv_find_secret() and publish Harald Freudenberger
2025-04-11 14:53 ` Holger Dengler
2025-04-14 8:08 ` Steffen Eiden
2025-04-14 15:15 ` Harald Freudenberger [this message]
2025-04-09 14:03 ` [PATCH v4 22/24] s390/pkey: Use preallocated memory for retrieve of UV secret metadata Harald Freudenberger
2025-04-11 15:24 ` Holger Dengler
2025-04-14 8:02 ` Steffen Eiden
2025-04-09 14:03 ` [PATCH v4 23/24] s390/zcrypt/pkey: Provide and pass xflags within pkey and zcrypt layers Harald Freudenberger
2025-04-11 14:36 ` Holger Dengler
2025-04-09 14:03 ` [PATCH v4 24/24] s390/pkey/crypto: Introduce xflags param for pkey in-kernel API Harald Freudenberger
2025-04-14 13:34 ` 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=34a5faeee685e97e80a53e00ec846af5@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=fcallies@linux.ibm.com \
--cc=frankja@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=imbrenda@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=seiden@linux.ibm.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