From: Janosch Frank <frankja@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v4 5/5] s390x: uv-guest: Add attestation tests
Date: Tue, 26 Apr 2022 11:22:03 +0200 [thread overview]
Message-ID: <ad44e7d2-6123-1981-b103-e5d9cc497c4c@linux.ibm.com> (raw)
In-Reply-To: <20220421094527.32261-6-seiden@linux.ibm.com>
On 4/21/22 11:45, Steffen Eiden wrote:
> Adds several tests to verify correct error paths of attestation.
>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
> ---
> lib/s390x/asm/uv.h | 5 +-
> s390x/Makefile | 1 +
> s390x/pv-attest.c | 225 +++++++++++++++++++++++++++++++++++++++++++++
> s390x/uv-guest.c | 13 ++-
> 4 files changed, 240 insertions(+), 4 deletions(-)
> create mode 100644 s390x/pv-attest.c
>
> diff --git a/lib/s390x/asm/uv.h b/lib/s390x/asm/uv.h
> index 7c8c399d..38920461 100644
> --- a/lib/s390x/asm/uv.h
> +++ b/lib/s390x/asm/uv.h
> @@ -108,7 +108,10 @@ struct uv_cb_qui {
> u8 reserved88[158 - 136]; /* 0x0088 */
> uint16_t max_guest_cpus; /* 0x009e */
> u64 uv_feature_indications; /* 0x00a0 */
> - u8 reserveda8[200 - 168]; /* 0x00a8 */
> + uint8_t reserveda8[224 - 168]; /* 0x00a8 */
> + uint64_t supp_att_hdr_ver; /* 0x00e0 */
> + uint64_t supp_paf; /* 0x00e8 */
> + uint8_t reservedf0[256 - 240]; /* 0x00f0 */
> } __attribute__((packed)) __attribute__((aligned(8)));
>
> struct uv_cb_cgc {
> diff --git a/s390x/Makefile b/s390x/Makefile
> index 8ff84db5..5a49d1e7 100644
> --- a/s390x/Makefile
> +++ b/s390x/Makefile
> @@ -29,6 +29,7 @@ tests += $(TEST_DIR)/mvpg-sie.elf
> tests += $(TEST_DIR)/spec_ex-sie.elf
> tests += $(TEST_DIR)/firq.elf
> tests += $(TEST_DIR)/epsw.elf
> +tests += $(TEST_DIR)/pv-attest.elf
>
> pv-tests += $(TEST_DIR)/pv-diags.elf
>
> diff --git a/s390x/pv-attest.c b/s390x/pv-attest.c
> new file mode 100644
> index 00000000..e31780a3
> --- /dev/null
> +++ b/s390x/pv-attest.c
> @@ -0,0 +1,225 @@
[...]
> +
> +static void test_attest_v1(uint64_t page)
> +{
> + struct uv_cb_attest uvcb = {
> + .header.cmd = UVC_CMD_ATTESTATION,
> + .header.len = sizeof(uvcb),
> + };
> + const struct uv_cb_qui *uvcb_qui = uv_get_query_data();
> + struct attest_request_v1 *attest_req = (void *)page;
> + struct uv_arcb_v1 *arcb = &attest_req->arcb;
> + int cc;
> +
> + report_prefix_push("v1");
> + if (!test_bit_inv(0, &uvcb_qui->supp_att_hdr_ver)) {
> + report_skip("Attestation version 1 not supported");
> + goto done;
> + }
> +
> + memset((void *)page, 0, PAGE_SIZE);
> +
> + /*
> + * Create a minimal arcb/uvcb such that FW has everything to start
> + * unsealing the request. However, this unsealing will fail as the
> + * kvm-unit-test framework provides no cryptography functions that
> + * would be needed to seal such requests.
> + */
> + arcb->req_ver = ARCB_VERSION_1;
> + arcb->req_len = sizeof(*arcb);
> + arcb->nks = 1;
> + arcb->sea = sizeof(arcb->meas_key);
> + arcb->plaint_att_flags = PAF_PHKH_ATT;
> + arcb->meas_alg_id = ARCB_MEAS_HMAC_SHA512;
> + uvcb.arcb_addr = (uint64_t)&attest_req->arcb;
> + uvcb.measurement_address = (uint64_t)attest_req->measurement;
> + uvcb.measurement_length = sizeof(attest_req->measurement);
> + uvcb.add_data_address = (uint64_t)attest_req->additional;
> + uvcb.add_data_length = sizeof(attest_req->additional);
> +
> + uvcb.continuation_token = 0xff;
> + cc = uv_call(0, (uint64_t)&uvcb);
> + report(cc == 1 && uvcb.header.rc == 0x0101, "invalid continuation token");
Please don't add the 0 to the front of the rc values.
[...]
> @@ -111,8 +120,6 @@ static void test_sharing(void)
> cc = uv_call(0, (u64)&uvcb);
> report(cc == 0 && uvcb.header.rc == UVC_RC_EXECUTED, "unshare");
> report_prefix_pop();
> -
> - report_prefix_pop();
That's unrelated, no?
> }
>
> static struct {
next prev parent reply other threads:[~2022-04-26 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 9:45 [kvm-unit-tests PATCH v4 0/5] s390x: Attestation tests Steffen Eiden
2022-04-21 9:45 ` [kvm-unit-tests PATCH v4 1/5] s390x: uv-host: Add invalid command attestation check Steffen Eiden
2022-04-21 9:45 ` [kvm-unit-tests PATCH v4 2/5] s390x: lib: Add QUI getter Steffen Eiden
2022-04-21 11:26 ` Janosch Frank
2022-04-21 9:45 ` [kvm-unit-tests PATCH v4 3/5] s390x: uv-guest: remove duplicated checks Steffen Eiden
2022-04-21 9:45 ` [kvm-unit-tests PATCH v4 4/5] s390x: uv-guest: add share bit test Steffen Eiden
2022-04-21 11:33 ` Janosch Frank
2022-04-21 9:45 ` [kvm-unit-tests PATCH v4 5/5] s390x: uv-guest: Add attestation tests Steffen Eiden
2022-04-26 9:22 ` Janosch Frank [this message]
2022-04-26 9:39 ` Steffen Eiden
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=ad44e7d2-6123-1981-b103-e5d9cc497c4c@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=seiden@linux.ibm.com \
--cc=thuth@redhat.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