From: Stefan Hajnoczi <stefanha@gmail.com>
To: Maria Kustova <maxa@catit.be>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, Maria Kustova <maria.k@catit.be>
Subject: Re: [Qemu-devel] [PATCH V5 0/5] tests: Add the image fuzzer with qcow2 support
Date: Fri, 8 Aug 2014 07:54:04 +0100 [thread overview]
Message-ID: <20140808065404.GC15209@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <cover.1407328960.git.maria.k@catit.be>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Wed, Aug 06, 2014 at 05:12:45PM +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.
>
> v4 -> v5:
> Runner:
> * Added a warning message if a backing file failed to be created (based on
> the review of Fam Zheng)
> * Back up a test image before every test command
> * Fixed always logged messages of a program under test
> * Added a warning message if a wrong name of a program under test is specified
> * Made offset and length qemu-io arguments multiple of a sector size
> * Print all errors to stderr
Can runner.py be moved to tests/image-fuzzer/runner.py?
That way it's immediately clear how to launch the fuzzer when looking at
the image-fuzzer/ directory.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-08-08 6:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 13:12 [Qemu-devel] [PATCH V5 0/5] tests: Add the image fuzzer with qcow2 support Maria Kustova
2014-08-06 13:12 ` [Qemu-devel] [PATCH V5 1/5] docs: Specification for the image fuzzer Maria Kustova
2014-08-08 6:17 ` Stefan Hajnoczi
2014-08-06 13:12 ` [Qemu-devel] [PATCH V5 2/5] runner: Tool for fuzz tests execution Maria Kustova
2014-08-08 6:52 ` Stefan Hajnoczi
2014-08-08 8:50 ` Fam Zheng
2014-08-08 8:58 ` M.Kustova
2014-08-08 11:08 ` Fam Zheng
2014-08-06 13:12 ` [Qemu-devel] [PATCH V5 3/5] fuzz: Fuzzing functions for qcow2 images Maria Kustova
2014-08-08 13:06 ` Stefan Hajnoczi
2014-08-06 13:12 ` [Qemu-devel] [PATCH V5 4/5] layout: Generator of fuzzed " Maria Kustova
2014-08-08 13:14 ` Stefan Hajnoczi
2014-08-06 13:12 ` [Qemu-devel] [PATCH V5 5/5] package: Public API for image-fuzzer/runner/runner.py Maria Kustova
2014-08-08 13:14 ` Stefan Hajnoczi
2014-08-08 6:54 ` Stefan Hajnoczi [this message]
2014-08-08 6:58 ` [Qemu-devel] [PATCH V5 0/5] tests: Add the image fuzzer with qcow2 support M.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=20140808065404.GC15209@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=maria.k@catit.be \
--cc=maxa@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).