qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Maria Kustova <maxa@catit.be>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
	Maria Kustova <maria.k@catit.be>
Subject: Re: [Qemu-devel] [PATCH V6 0/5] tests: Add the image fuzzer with qcow2 support
Date: Thu, 14 Aug 2014 20:56:32 +0100	[thread overview]
Message-ID: <20140814195632.GA27302@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <cover.1407752590.git.maria.k@catit.be>

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

On Mon, Aug 11, 2014 at 02:33:57PM +0400, Maria Kustova wrote:
> 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.
> 
> v5 -> v6:
>    * Moved the image fuzzer specification to the QEMU docs directory
>    * Moved the runner.py to the image fuzzer root directory
> 
> 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
> 
>  docs/image-fuzzer.txt                | 239 +++++++++++++++++++++
>  tests/image-fuzzer/qcow2/__init__.py |   1 +
>  tests/image-fuzzer/qcow2/fuzz.py     | 327 ++++++++++++++++++++++++++++
>  tests/image-fuzzer/qcow2/layout.py   | 369 +++++++++++++++++++++++++++++++
>  tests/image-fuzzer/runner.py         | 405 +++++++++++++++++++++++++++++++++++
>  5 files changed, 1341 insertions(+)
>  create mode 100644 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.py

Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

      parent reply	other threads:[~2014-08-14 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 10:33 [Qemu-devel] [PATCH V6 0/5] tests: Add the image fuzzer with qcow2 support Maria Kustova
2014-08-11 10:33 ` [Qemu-devel] [PATCH V6 1/5] docs: Specification for the image fuzzer Maria Kustova
2014-08-11 10:33 ` [Qemu-devel] [PATCH V6 2/5] runner: Tool for fuzz tests execution Maria Kustova
2014-08-11 10:34 ` [Qemu-devel] [PATCH V6 3/5] fuzz: Fuzzing functions for qcow2 images Maria Kustova
2014-08-11 10:34 ` [Qemu-devel] [PATCH V6 4/5] layout: Generator of fuzzed " Maria Kustova
2014-08-11 10:34 ` [Qemu-devel] [PATCH V6 5/5] package: Public API for image-fuzzer/runner/runner.py Maria Kustova
2014-08-14 19:56 ` Stefan Hajnoczi [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=20140814195632.GA27302@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=maria.k@catit.be \
    --cc=maxa@catit.be \
    --cc=qemu-devel@nongnu.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).