public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Shuah Khan <shuah@kernel.org>, Nico Boehr <nrb@linux.ibm.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/4] s390: Ultravisor device
Date: Wed, 16 Mar 2022 10:04:41 +0100	[thread overview]
Message-ID: <7268565b-bb34-43fa-463e-8b9bf732b721@linux.ibm.com> (raw)
In-Reply-To: <20220304141141.32767-1-seiden@linux.ibm.com>

On 3/4/22 15:11, Steffen Eiden wrote:
> This series adds an Ultravisor(UV) device letting the userspace send some
> Ultravisor calls to the UV. Currently two calls are supported.
> Query Ultravisor Information (QUI) and
> Receive Attestation Measurement (Attest[ation]).
> 
> The UV device is implemented as a miscdevice accepting only IOCTLs.
> The IOCTL cmd specifies the UV call and the IOCTL arg the request
> and response data depending on the UV call.
> The device driver writes the UV response in the ioctl argument data.
> 
> The 'uvdevice' does no checks on the request beside faulty userspace
> addresses, if sizes are in a sane range before allocating in kernel space,
> and other tests that prevent the system from corruption.
> Especially, no checks are made, that will be performed by the UV anyway
> (E.g. 'invalid command' in case of attestation on unsupported hardware).
> These errors are reported back to Userspace using the UV return code
> field.
> 
> The first two patches introduce the new device as a module configured to be
> compiled directly into the kernel (y) similar to the s390 SCLP and CHSH
> miscdevice modules. Patch 3&4 introduce Kselftests which verify error
> paths of the ioctl.

Please fixup the commit message in the first patch and then push patches 
#1 and #3 to devel so we get CI coverage.

For now I'd opt to not include the qui patches but please put them on a 
branch. They might prove to be useful at a later time.

> 
> v2->v3:
>     The main change is that QUI is now introduced after Attestation as we
>     might not want pick it. Also the Kselftest patch is splitted into
>     Attestation and QUI so that they can be picked without requiring
>     QUI support of the uvdevice.
> 
>    * dropped the Kconfig dependency
>    * reorganized the series:
>      - Patch 1 now covers the introduction of the uvdevice and Attestation
>      - Patch 2 adds QUI to uvdevice
>      - Patch 3/4 add Kselftests for Attestation and QUI
>    * fixed some nits
>    * added some comments
> 
> v1->v2:
>    * ioctl returns -ENOIOCTLCMD in case of a invalid ioctl command
>    * streamlined reserved field test
>    * default Kconfig is y instead of m
>    * improved selftest documentation
> 
> Steffen Eiden (4):
>    drivers/s390/char: Add Ultravisor io device
>    drivers/s390/char: Add Query Ultravisor Information to uvdevice
>    selftests: drivers/s390x: Add uvdevice tests
>    selftests: drivers/s390x: Add uvdevice  QUI tests
> 
>   MAINTAINERS                                   |   3 +
>   arch/s390/include/asm/uv.h                    |  23 +-
>   arch/s390/include/uapi/asm/uvdevice.h         |  53 +++
>   drivers/s390/char/Kconfig                     |  10 +
>   drivers/s390/char/Makefile                    |   1 +
>   drivers/s390/char/uvdevice.c                  | 320 ++++++++++++++++++
>   tools/testing/selftests/Makefile              |   1 +
>   tools/testing/selftests/drivers/.gitignore    |   1 +
>   .../selftests/drivers/s390x/uvdevice/Makefile |  22 ++
>   .../selftests/drivers/s390x/uvdevice/config   |   1 +
>   .../drivers/s390x/uvdevice/test_uvdevice.c    | 281 +++++++++++++++
>   11 files changed, 715 insertions(+), 1 deletion(-)
>   create mode 100644 arch/s390/include/uapi/asm/uvdevice.h
>   create mode 100644 drivers/s390/char/uvdevice.c
>   create mode 100644 tools/testing/selftests/drivers/s390x/uvdevice/Makefile
>   create mode 100644 tools/testing/selftests/drivers/s390x/uvdevice/config
>   create mode 100644 tools/testing/selftests/drivers/s390x/uvdevice/test_uvdevice.c
> 


      parent reply	other threads:[~2022-03-16  9:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 14:11 [PATCH v3 0/4] s390: Ultravisor device Steffen Eiden
2022-03-04 14:11 ` [PATCH v3 1/4] drivers/s390/char: Add Ultravisor io device Steffen Eiden
2022-03-16  8:23   ` Janosch Frank
2022-03-16  9:02   ` Janosch Frank
2022-03-17  9:47   ` [PATCH v3 1/4] drivers/s390/char: Add Ultravisor io device' Steffen Eiden
2022-03-17  9:59     ` Greg KH
2022-03-17 11:07       ` [PATCH v3 1/4] drivers/s390/char: Add Ultravisor io device Steffen Eiden
2022-03-17 11:23         ` Steffen Eiden
2022-03-17 11:59         ` Greg KH
2022-03-04 14:11 ` [PATCH v3 2/4] drivers/s390/char: Add Query Ultravisor Information to uvdevice Steffen Eiden
2022-03-16  8:56   ` Janosch Frank
2022-03-04 14:11 ` [PATCH v3 3/4] selftests: drivers/s390x: Add uvdevice tests Steffen Eiden
2022-03-04 14:11 ` [PATCH v3 4/4] selftests: drivers/s390x: Add uvdevice QUI tests Steffen Eiden
2022-03-16  9:04 ` Janosch Frank [this message]

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=7268565b-bb34-43fa-463e-8b9bf732b721@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=seiden@linux.ibm.com \
    --cc=shuah@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