From: Nico Boehr <nrb@linux.ibm.com>
To: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com,
david@redhat.com, farman@linux.ibm.com
Subject: [kvm-unit-tests PATCH v1 1/9] s390x: smp: add tests for several invalid SIGP orders
Date: Mon, 21 Mar 2022 11:18:56 +0100 [thread overview]
Message-ID: <20220321101904.387640-2-nrb@linux.ibm.com> (raw)
In-Reply-To: <20220321101904.387640-1-nrb@linux.ibm.com>
Add tests with for intercepted SIGP orders with invalid values:
- SIGP_STOP with invalid CPU address
- SIGP_START with invalid CPU address
- SIGP_CPU_RESET with invalid CPU address
- SIGP_STOP_AND_STORE_STATUS with invalid CPU address
- SIGP_STORE_STATUS_AT_ADDRESS with invalid CPU address
- invalid order
- invalid order with invalid CPU address
Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
---
s390x/smp.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
diff --git a/s390x/smp.c b/s390x/smp.c
index 068ac74dd28a..911a26c51b10 100644
--- a/s390x/smp.c
+++ b/s390x/smp.c
@@ -19,6 +19,47 @@
#include <alloc_page.h>
static int testflag = 0;
+#define INVALID_CPU_ADDRESS -4711
+#define INVALID_ORDER_CODE 0xFF
+struct sigp_invalid_cases {
+ int order;
+ char message[100];
+};
+static const struct sigp_invalid_cases cases_invalid_cpu_addr[] = {
+ { SIGP_STOP, "stop with invalid CPU address" },
+ { SIGP_START, "start with invalid CPU address" },
+ { SIGP_CPU_RESET, "reset with invalid CPU address" },
+ { INVALID_ORDER_CODE, "invalid order code and CPU address" },
+ { SIGP_SENSE, "sense with invalid CPU address" },
+ { SIGP_STOP_AND_STORE_STATUS, "stop and store status with invalid CPU address" },
+};
+static const struct sigp_invalid_cases cases_valid_cpu_addr[] = {
+ { INVALID_ORDER_CODE, "invalid order code" },
+};
+
+static void test_invalid(void)
+{
+ const struct sigp_invalid_cases *c;
+ uint32_t status;
+ int cc;
+ int i;
+
+ report_prefix_push("invalid parameters");
+
+ for (i = 0; i < ARRAY_SIZE(cases_invalid_cpu_addr); i++) {
+ c = &cases_invalid_cpu_addr[i];
+ cc = sigp(INVALID_CPU_ADDRESS, c->order, 0, &status);
+ report(cc == 3, c->message);
+ }
+
+ for (i = 0; i < ARRAY_SIZE(cases_valid_cpu_addr); i++) {
+ c = &cases_valid_cpu_addr[i];
+ cc = smp_sigp(1, c->order, 0, &status);
+ report(cc == 1, c->message);
+ }
+
+ report_prefix_pop();
+}
static void wait_for_flag(void)
{
@@ -123,10 +164,16 @@ static void test_store_status(void)
{
struct cpu_status *status = alloc_pages_flags(1, AREA_DMA31);
uint32_t r;
+ int cc;
report_prefix_push("store status at address");
memset(status, 0, PAGE_SIZE * 2);
+ report_prefix_push("invalid CPU address");
+ cc = sigp(INVALID_CPU_ADDRESS, SIGP_STORE_STATUS_AT_ADDRESS, (uintptr_t)status, &r);
+ report(cc == 3, "returned with CC = 3");
+ report_prefix_pop();
+
report_prefix_push("running");
smp_cpu_restart(1);
smp_sigp(1, SIGP_STORE_STATUS_AT_ADDRESS, (uintptr_t)status, &r);
@@ -331,6 +378,7 @@ int main(void)
smp_cpu_stop(1);
test_start();
+ test_invalid();
test_restart();
test_stop();
test_stop_store_status();
--
2.31.1
next prev parent reply other threads:[~2022-03-21 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 10:18 [kvm-unit-tests PATCH v1 0/9] s390x: Further extend instruction interception tests Nico Boehr
2022-03-21 10:18 ` Nico Boehr [this message]
2022-03-21 10:18 ` [kvm-unit-tests PATCH v1 2/9] s390x: smp: stop already stopped CPU Nico Boehr
2022-03-21 10:18 ` [kvm-unit-tests PATCH v1 3/9] s390x: gs: move to new header file Nico Boehr
2022-03-21 10:18 ` [kvm-unit-tests PATCH v1 4/9] s390x: smp: add test for SIGP_STORE_ADTL_STATUS order Nico Boehr
2022-03-21 14:59 ` Claudio Imbrenda
2022-03-23 14:19 ` Nico Boehr
2022-03-23 15:47 ` Claudio Imbrenda
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 5/9] s390x: smp: add tests for SET_PREFIX Nico Boehr
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 6/9] s390x: smp: add test for EMERGENCY_SIGNAL with invalid CPU address Nico Boehr
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 7/9] s390x: smp: add tests for CONDITIONAL EMERGENCY Nico Boehr
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 8/9] s390x: add TPROT tests Nico Boehr
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 9/9] s390x: stsi: check zero and ignored bits in r0 and r1 Nico Boehr
2022-03-21 15:01 ` [kvm-unit-tests PATCH v1 0/9] s390x: Further extend instruction interception tests Claudio Imbrenda
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=20220321101904.387640-2-nrb@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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