linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
	Dan Williams <dan.j.williams@intel.com>,
	<linux-coco@lists.linux.dev>
Cc: Borislav Petkov <bp@alien8.de>,
	Dionna Glaze <dionnaglaze@google.com>,
	Brijesh Singh <brijesh.singh@amd.com>, <peterz@infradead.org>,
	<x86@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/5] virt: sevguest: Prep for kernel internal {get, get_ext}_report()
Date: Tue, 15 Aug 2023 14:37:01 -0700	[thread overview]
Message-ID: <64dbeffcf243a_47b5729487@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <ab871b36-203c-6b40-f5e4-2dfc4b15b41d@amd.com>

Tom Lendacky wrote:
> On 8/14/23 02:43, Dan Williams wrote:
> > In preparation for using the TSM key facility to convey attestation blobs
> > to userspace, add an argument to flag whether @arg is a user buffer or a
> > kernel buffer.
> > 
> > While TSM keys is meant to replace existing confidenital computing
> 
> s/confidenital/confidential/
> 
> > ioctl() implementations for attestation report retrieval the old ioctl()
> > path needs to stick around for a deprecation period.
> > 
> > No behavior change intended, just introduce the copy wrappers and @type
> > argument.
> > 
> > Note that these wrappers are similar to copy_{to,from}_sockptr(). If
> > this approach moves forward that concept is something that can be
> > generalized into a helper with a generic name.
> > 
> > Cc: Borislav Petkov <bp@alien8.de>
> > Cc: Tom Lendacky <thomas.lendacky@amd.com>
> > Cc: Dionna Glaze <dionnaglaze@google.com>
> > Cc: Brijesh Singh <brijesh.singh@amd.com>
> > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> > ---
> >   drivers/virt/coco/sev-guest/sev-guest.c |   48 ++++++++++++++++++++++++-------
> >   1 file changed, 37 insertions(+), 11 deletions(-)
> > 
> > diff --git a/drivers/virt/coco/sev-guest/sev-guest.c b/drivers/virt/coco/sev-guest/sev-guest.c
> > index 97dbe715e96a..f48c4764a7a2 100644
> > --- a/drivers/virt/coco/sev-guest/sev-guest.c
> > +++ b/drivers/virt/coco/sev-guest/sev-guest.c
> > @@ -470,7 +470,32 @@ static int handle_guest_request(struct snp_guest_dev *snp_dev, u64 exit_code,
> >   	return 0;
> >   }
> >   
> > -static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_ioctl *arg)
> > +enum snp_arg_type {
> > +	SNP_UARG,
> > +	SNP_KARG,
> > +};
> > +
> > +static unsigned long copy_from(void *to, unsigned long from, unsigned long n,
> > +			       enum snp_arg_type type)
> > +{
> > +	if (type == SNP_UARG)
> > +		return copy_from_user(to, (void __user *)from, n);
> 
> I'm a fan of blank lines to make reading functions easier. A blank line 
> here and below after the memcpy() would be nice.
> 
> Ditto in the copy_to() function.
> 
> > +	memcpy(to, (void *)from, n);
> > +	return 0;
> > +}
> > +
> > +static unsigned long copy_to(unsigned long to, const void *from,
> > +			     unsigned long n, enum snp_arg_type type)
> > +{
> > +	if (type == SNP_UARG)
> > +		return copy_to_user((void __user *)to, from, n);
> > +	memcpy((void *)to, from, n);
> > +	return 0;
> > +}
> > +
> > +static int get_report(struct snp_guest_dev *snp_dev,
> > +		      struct snp_guest_request_ioctl *arg,
> > +		      enum snp_arg_type type)
> 
> You can go out to 100 characters now, so you can put "struct .. *arg" on 
> the top line and just put the enum on a new line.
> 
> >   {
> >   	struct snp_guest_crypto *crypto = snp_dev->crypto;
> >   	struct snp_report_resp *resp;
> > @@ -482,7 +507,7 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_io
> >   	if (!arg->req_data || !arg->resp_data)
> >   		return -EINVAL;
> >   
> > -	if (copy_from_user(&req, (void __user *)arg->req_data, sizeof(req)))
> > +	if (copy_from(&req, arg->req_data, sizeof(req), type))
> >   		return -EFAULT;
> >   
> >   	/*
> > @@ -501,7 +526,7 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_io
> >   	if (rc)
> >   		goto e_free;
> >   
> > -	if (copy_to_user((void __user *)arg->resp_data, resp, sizeof(*resp)))
> > +	if (copy_to(arg->resp_data, resp, sizeof(*resp), type))
> >   		rc = -EFAULT;
> >   
> >   e_free:
> > @@ -550,7 +575,9 @@ static int get_derived_key(struct snp_guest_dev *snp_dev, struct snp_guest_reque
> >   	return rc;
> >   }
> >   
> > -static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_ioctl *arg)
> > +static int get_ext_report(struct snp_guest_dev *snp_dev,
> > +			  struct snp_guest_request_ioctl *arg,
> > +			  enum snp_arg_type type)
> 
> Ditto here on the 100 characters.
> 
> >   {
> >   	struct snp_guest_crypto *crypto = snp_dev->crypto;
> >   	struct snp_ext_report_req req;
> > @@ -562,7 +589,7 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques
> >   	if (!arg->req_data || !arg->resp_data)
> >   		return -EINVAL;
> >   
> > -	if (copy_from_user(&req, (void __user *)arg->req_data, sizeof(req)))
> > +	if (copy_from(&req, arg->req_data, sizeof(req), type))
> >   		return -EFAULT;
> >   
> >   	/* userspace does not want certificate data */
> > @@ -611,14 +638,13 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques
> >   	if (ret)
> >   		goto e_free;
> >   
> > -	if (npages &&
> > -	    copy_to_user((void __user *)req.certs_address, snp_dev->certs_data,
> > -			 req.certs_len)) {
> > +	if (npages && copy_to(req.certs_address, snp_dev->certs_data,
> > +			      req.certs_len, type)) {
> 
> This can also be a single line now.

So the kernel's .clang-format template still enforces the 80 column
limit. I am ok to bump that to 100 temporarily for my edits to this
file, but in general I tend to just let clang-format do its thing. One
less thing to worry about.

  reply	other threads:[~2023-08-15 21:37 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14  7:43 [PATCH v2 0/5] tsm: Attestation Report ABI Dan Williams
2023-08-14  7:43 ` [PATCH v2 1/5] virt: coco: Add a coco/Makefile and coco/Kconfig Dan Williams
2023-08-14  7:43 ` [PATCH v2 2/5] tsm: Introduce a shared ABI for attestation reports Dan Williams
2023-08-14  8:24   ` Jeremi Piotrowski
2023-08-14 16:21     ` Dan Williams
2023-08-14 15:38   ` Greg Kroah-Hartman
2023-08-14 16:43     ` Dan Williams
2023-08-14 18:43       ` Greg Kroah-Hartman
2023-08-15 19:51   ` Tom Lendacky
2023-08-16 14:44   ` Tom Lendacky
2023-08-16 15:12     ` Dan Williams
2023-08-22  7:29   ` Roy Hopkins
2023-08-23 13:49   ` Samuel Ortiz
2023-08-28 10:46     ` Dr. Greg
2023-08-14  7:43 ` [PATCH v2 3/5] virt: sevguest: Prep for kernel internal {get, get_ext}_report() Dan Williams
2023-08-14 16:58   ` Dionna Amalie Glaze
2023-08-14 23:24     ` Dan Williams
2023-08-15 20:11       ` Tom Lendacky
2023-08-15 21:03         ` Dan Williams
2023-08-16 19:38           ` Dionna Amalie Glaze
2023-08-15 20:20   ` Tom Lendacky
2023-08-15 21:37     ` Dan Williams [this message]
2023-08-14  7:43 ` [PATCH v2 4/5] mm/slab: Add __free() support for kvfree Dan Williams
2023-08-14 15:31   ` Greg Kroah-Hartman
2023-08-14 16:17     ` Peter Zijlstra
2023-08-14 18:44       ` Greg Kroah-Hartman
2023-08-14 18:45         ` Greg Kroah-Hartman
2024-01-04  6:57       ` Lukas Wunner
2024-01-04 18:29         ` Dan Williams
2023-08-14  7:43 ` [PATCH v2 5/5] virt: sevguest: Add TSM_REPORTS support for SNP_{GET, GET_EXT}_REPORT Dan Williams
2023-08-14  8:30   ` Jeremi Piotrowski
2023-08-14 16:22     ` Dan Williams
2023-08-14 11:21   ` Peter Zijlstra
2023-08-14 16:25     ` Dan Williams
2023-08-14 16:48       ` Peter Zijlstra
2023-08-14 22:15         ` Peter Zijlstra
2023-08-15  8:37           ` Peter Zijlstra
2023-08-15 20:50   ` Tom Lendacky
2023-08-15 21:40     ` Dan Williams
2023-08-14  9:04 ` [PATCH v2 0/5] tsm: Attestation Report ABI Jeremi Piotrowski
2023-08-14 17:12   ` Dan Williams
2023-08-15 14:27     ` Peter Gonda
2023-08-15 17:16       ` Dionna Amalie Glaze
2023-08-15 21:13         ` Dan Williams
2023-08-15 18:13       ` Dan Williams
2023-08-16  9:42     ` Jeremi Piotrowski
2023-08-23 11:21   ` Dr. Greg

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=64dbeffcf243a_47b5729487@dwillia2-mobl3.amr.corp.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=bp@alien8.de \
    --cc=brijesh.singh@amd.com \
    --cc=dionnaglaze@google.com \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=thomas.lendacky@amd.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).