From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Steffen Eiden" <seiden@linux.ibm.com>,
<linux-kernel@vger.kernel.org>, <linux-s390@vger.kernel.org>
Cc: "Ingo Franzki" <ifranzki@linux.ibm.com>,
"Harald Freudenberger" <freude@linux.ibm.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>
Subject: Re: [PATCH v1 5/6] s390/uvdevice: Add List Secrets Ext IOCTL
Date: Tue, 01 Oct 2024 18:19:50 +0200 [thread overview]
Message-ID: <D4KLU6A3D449.1P07EI9XL7IY2@linux.ibm.com> (raw)
In-Reply-To: <20240930131909.2079965-6-seiden@linux.ibm.com>
On Mon Sep 30, 2024 at 3:19 PM CEST, Steffen Eiden wrote:
> Add an extended List Secrets IOCTL. In contrast to the first list IOCTL
> this accepts an index as the first two bytes of the provided page as an
> input. This index is then taken as the index offset for the list UVC to
> receive later entries for the list.
>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
[...]
> +/* The actual list(_ext) IOCTL.
> + * If list_ext is true, the first two bytes of the user buffer set the starting index of the
> + * list-UVC
> + */
> +static int list_secrets(struct uvio_ioctl_cb *uv_ioctl, bool list_ext)
> +{
> + void __user *user_buf_arg = (void __user *)uv_ioctl->argument_addr;
> + u16 __user *user_index = (u16 __user *)uv_ioctl->argument_addr;
> + u16 start_idx = 0;
> + u8 *secrets = NULL;
> + int ret;
nit: These can be reordered to reverse xmas tree.
> +
> + if (uv_ioctl->argument_len != UVIO_LIST_SECRETS_LEN)
> + return -EINVAL;
> +
> + BUILD_BUG_ON(UVIO_LIST_SECRETS_LEN != PAGE_SIZE);
> + secrets = (u8 *)get_zeroed_page(GFP_KERNEL);
> + if (!secrets)
> + return -ENOMEM;
> +
> + // The extended call accepts an u16 index as input
Comments should use /* */
> + ret = -EFAULT;
> + if (list_ext) {
> + if (get_user(start_idx, user_index))
> + goto err;
> + }
> +
> + uv_list_secrets(secrets, start_idx, &uv_ioctl->uv_rc, &uv_ioctl->uv_rrc);
> +
> + if (copy_to_user(user_buf_arg, secrets, UVIO_LIST_SECRETS_LEN))
> + goto err;
> + ret = 0;
> +
> +err:
> + free_pages((unsigned long)secrets, 0);
> + return ret;
> +}
[...]
next prev parent reply other threads:[~2024-10-01 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 13:19 [PATCH v1 0/6] s390/uv: Retrieve Secrets Ultravisor Call support Steffen Eiden
2024-09-30 13:19 ` [PATCH v1 1/6] s390/boot/uv.c: Use a constant for more-data rc Steffen Eiden
2024-10-01 12:10 ` Claudio Imbrenda
2024-10-01 13:56 ` Janosch Frank
2024-09-30 13:19 ` [PATCH v1 2/6] s390/uv: Retrieve UV secrets support Steffen Eiden
2024-10-01 16:06 ` Christoph Schlameuss
2024-10-02 7:51 ` Janosch Frank
2024-09-30 13:19 ` [PATCH v1 3/6] s390/uvdevice: Add Retrieve Secret IOCTL Steffen Eiden
2024-10-01 16:09 ` Christoph Schlameuss
2024-09-30 13:19 ` [PATCH v1 4/6] s390/uvdevice: Increase indent in IOCTL definitions Steffen Eiden
2024-09-30 13:19 ` [PATCH v1 5/6] s390/uvdevice: Add List Secrets Ext IOCTL Steffen Eiden
2024-10-01 16:19 ` Christoph Schlameuss [this message]
2024-09-30 13:19 ` [PATCH v1 6/6] s390/uv: Retrieve UV secrets sysfs support Steffen Eiden
2024-10-01 17:42 ` Christoph Schlameuss
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=D4KLU6A3D449.1P07EI9XL7IY2@linux.ibm.com \
--to=schlameuss@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=ifranzki@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.