kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: autotest@test.kernel.org
Cc: kvm@vger.kernel.org, Jason Wang <jasowang@redhat.com>
Subject: [PATCH] KVM test: Add a subtest iofuzz
Date: Thu,  6 May 2010 20:13:28 -0300	[thread overview]
Message-ID: <1273187608-27605-1-git-send-email-lmr@redhat.com> (raw)

From: Jason Wang <jasowang@redhat.com>

The design of iofuzz is simple: it just generate random I/O port
activity inside the virtual machine. The correctness of the device
emulation may be verified through this test.

As the instrcutions are randomly generated, guest may enter the wrong
state. The test solve this issue by detect the hang and restart the
virtual machine.

The test duration could also be adjusted through the "fuzz_count". And
the parameter "skip_devices" is used to specified the devices which
should not be used to do the fuzzing.

For current version, every activity were logged and the commnad was
sent through a seesion between host and guest. Through this method may
slow down the whole test but it works well. The enumeration was done
through /proc/ioports and the scenario of avtivity is not aggressive.

Suggestions are welcome.

Signed-off-by: Jason Wang <jasowang@redhat.com>
---
 client/tests/kvm/tests/iofuzz.py       |  138 ++++++++++++++++++++++++++++++++
 client/tests/kvm/tests_base.cfg.sample |    2 +
 2 files changed, 140 insertions(+), 0 deletions(-)
 create mode 100644 client/tests/kvm/tests/iofuzz.py

diff --git a/client/tests/kvm/tests/iofuzz.py b/client/tests/kvm/tests/iofuzz.py
new file mode 100644
index 0000000..5bd1b8e
--- /dev/null
+++ b/client/tests/kvm/tests/iofuzz.py
@@ -0,0 +1,138 @@
+import logging, time, re, random
+from autotest_lib.client.common_lib import error
+import kvm_subprocess, kvm_test_utils, kvm_utils
+
+
+def run_iofuzz(test, params, env):
+    """
+    KVM iofuzz test:
+    1) Log into a guest
+    2) Enumerate all IO port ranges through /proc/ioports
+    3) On each port of the range:
+        * Read it
+        * Write 0 to it
+        * Write a random value to a random port on a random order
+
+    If the guest SSH session hangs, the test detects the hang and the guest
+    is then rebooted. The test fails if we detect the qemu process to terminate
+    while executing the process.
+
+    @param test: kvm test object
+    @param params: Dictionary with the test parameters
+    @param env: Dictionary with test environment.
+    """
+    def outb(session, port, data):
+        """
+        Write data to a given port.
+
+        @param session: SSH session stablished to a VM
+        @param port: Port where we'll write the data
+        @param data: Integer value that will be written on the port. This
+                value will be converted to octal before its written.
+        """
+        logging.debug("outb(0x%x, 0x%x)", port, data)
+        outb_cmd = ("echo -e '\\%s' | dd of=/dev/port seek=%d bs=1 count=1" %
+                    (oct(data), port))
+        s, o = session.get_command_status_output(outb_cmd)
+        if s is None:
+            logging.debug("Command did not return")
+        if s != 0:
+            logging.debug("Command returned status %s", s)
+
+
+    def inb(session, port):
+        """
+        Read from a given port.
+
+        @param session: SSH session stablished to a VM
+        @param port: Port where we'll read data
+        """
+        logging.debug("inb(0x%x)", port)
+        inb_cmd = "dd if=/dev/port seek=%d of=/dev/null bs=1 count=1" % port
+        s, o = session.get_command_status_output(inb_cmd)
+        if s is None:
+            logging.debug("Command did not return")
+        if s != 0:
+            logging.debug("Command returned status %s", s)
+
+
+    def fuzz(session, inst_list):
+        """
+        Executes a series of read/write/randwrite instructions.
+
+        If the guest SSH session hangs, an attempt to relogin will be made.
+        If it fails, the guest will be reset. If during the process the VM
+        process abnormally ends, the test fails.
+
+        @param inst_list: List of instructions that will be executed.
+        @raise error.TestFail: If the VM process dies in the middle of the
+                fuzzing procedure.
+        """
+        for (op, operand) in inst_list:
+            if op == "read":
+                inb(session, operand[0])
+            elif op =="write":
+                outb(session, operand[0], operand[1])
+            else:
+                raise error.TestError("Unknown command %s" % op)
+
+            if not session.is_responsive():
+                logging.debug("Session is not responsive")
+                if vm.process.is_alive():
+                    logging.debug("VM is alive, try to re-login")
+                    try:
+                        session = kvm_test_utils.wait_for_login(vm, 0, 10, 0, 2)
+                    except:
+                        logging.debug("Could not re-login, reboot the guest")
+                        session = kvm_test_utils.reboot(vm, session,
+                                                        method = "system_reset")
+                else:
+                    raise error.TestFail("VM has quit abnormally during %s",
+                                         (op, operand))
+
+
+    boot_timeout = float(params.get("boot_timeout", 240))
+    vm = kvm_test_utils.get_living_vm(env, params.get("main_vm"))
+    session = kvm_test_utils.wait_for_login(vm, 0, boot_timeout, 0, 2)
+
+    try:
+        ports = {}
+        r = random.SystemRandom()
+
+        logging.info("Enumerate guest devices through /proc/ioports")
+        ioports = session.get_command_output("cat /proc/ioports")
+        logging.debug(ioports)
+        devices = re.findall("(\w+)-(\w+)\ : (.*)", ioports)
+
+        skip_devices = params.get("skip_devices","")
+        fuzz_count = int(params.get("fuzz_count", 10))
+
+        for (beg, end, name) in devices:
+            ports[(int(beg, base=16), int(end, base=16))] = name.strip()
+
+        for (beg, end) in ports.keys():
+            name = ports[(beg, end)]
+            if name in skip_devices:
+                logging.info("Skipping device %s", name)
+                continue
+
+            logging.info("Fuzzing %s, port range 0x%x-0x%x", name, beg, end)
+            inst = []
+
+            # Read all ports of the range
+            for port in range(beg, end + 1):
+                inst.append(("read", [port]))
+
+            # Write 0 to all ports of the range
+            for port in range(beg, end + 1):
+                inst.append(("write", [port, 0]))
+
+            # Write random values to random ports of the range
+            for seq in range(fuzz_count * (end - beg + 1)):
+                inst.append(("write",
+                             [r.randint(beg, end), r.randint(0,255)]))
+
+            fuzz(session, inst)
+
+    finally:
+        session.close()
diff --git a/client/tests/kvm/tests_base.cfg.sample b/client/tests/kvm/tests_base.cfg.sample
index 2d56069..bb3646c 100644
--- a/client/tests/kvm/tests_base.cfg.sample
+++ b/client/tests/kvm/tests_base.cfg.sample
@@ -313,6 +313,8 @@ variants:
                 ksm_mode = "serial"
             - ksm_parallel:
                 ksm_mode = "parallel"
+    - iofuzz:
+        type = iofuzz
 
     # This unit test module is for older branches of KVM that use the
     # kvmctl test harness (such as the code shipped with RHEL 5.x)
-- 
1.7.0.1


             reply	other threads:[~2010-05-06 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 23:13 Lucas Meneghel Rodrigues [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-07 11:55 [PATCH] KVM test: Add a subtest iofuzz Jason Wang

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=1273187608-27605-1-git-send-email-lmr@redhat.com \
    --to=lmr@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.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).