qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Maria Kustova <maxa@catit.be>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com,
	Maria Kustova <maria.k@catit.be>,
	stefanha@redhat.com
Subject: [Qemu-devel] [PATCH V4 0/5] tests: Add the image fuzzer with qcow2 support
Date: Mon, 21 Jul 2014 14:18:07 +0400	[thread overview]
Message-ID: <cover.1405935974.git.maria.k@catit.be> (raw)

This patch series introduces the image fuzzer, a tool for stability and
reliability testing.
Its approach is to run large amount of tests in background. During every test a
program (e.g. qemu-img) is called to read or modify an invalid test image.
A test image has valid inner structure defined by its format specification with
some fields having random invalid values.

Patch 1 contains documentation for the image fuzzer, patch 2 is the test runner
and remaining ones relate to the image generator for qcow2 format.

This patch series was created for the 'block-next' branch.

v3 -> v4:
All changes are based on the review of Stefan Hajnoczi:
Runner:
 * list of test results replaced by a single boolean value
 * the code cleanup (residual hash() and error handling)
 * fixed ambiguities in the usage and errors texts
Fuzz:
 * simplified validating and selecting functions with the unified validator
Layout:
 * fixed typos
Docs:
 * fixed wrong JSON terminology

Maria Kustova (5):
  docs: Specification for the image fuzzer
  runner: Tool for fuzz tests execution
  fuzz: Fuzzing functions for qcow2 images
  layout: Generator of fuzzed qcow2 images
  package: Public API for image-fuzzer/runner/runner.py

 tests/image-fuzzer/docs/image-fuzzer.txt | 239 ++++++++++++++++++++
 tests/image-fuzzer/qcow2/__init__.py     |   1 +
 tests/image-fuzzer/qcow2/fuzz.py         | 329 ++++++++++++++++++++++++++++
 tests/image-fuzzer/qcow2/layout.py       | 359 ++++++++++++++++++++++++++++++
 tests/image-fuzzer/runner/runner.py      | 360 +++++++++++++++++++++++++++++++
 5 files changed, 1288 insertions(+)
 create mode 100644 tests/image-fuzzer/docs/image-fuzzer.txt
 create mode 100644 tests/image-fuzzer/qcow2/__init__.py
 create mode 100644 tests/image-fuzzer/qcow2/fuzz.py
 create mode 100644 tests/image-fuzzer/qcow2/layout.py
 create mode 100755 tests/image-fuzzer/runner/runner.py

-- 
1.9.3

             reply	other threads:[~2014-07-21 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 10:18 Maria Kustova [this message]
2014-07-21 10:18 ` [Qemu-devel] [PATCH V4 1/5] docs: Specification for the image fuzzer Maria Kustova
2014-07-21 10:18 ` [Qemu-devel] [PATCH V4 2/5] runner: Tool for fuzz tests execution Maria Kustova
2014-07-24  3:30   ` Fam Zheng
2014-08-01  5:46   ` Stefan Hajnoczi
2014-08-04  9:28     ` M.Kustova
2014-07-21 10:18 ` [Qemu-devel] [PATCH V4 3/5] fuzz: Fuzzing functions for qcow2 images Maria Kustova
2014-08-01  5:55   ` Stefan Hajnoczi
2014-07-21 10:18 ` [Qemu-devel] [PATCH V4 4/5] layout: Generator of fuzzed " Maria Kustova
2014-07-21 10:18 ` [Qemu-devel] [PATCH V4 5/5] package: Public API for image-fuzzer/runner/runner.py Maria Kustova

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=cover.1405935974.git.maria.k@catit.be \
    --to=maxa@catit.be \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=maria.k@catit.be \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).