From: Kevin Wolf <kwolf@redhat.com>
To: "M.Kustova" <maria.k@catit.be>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Disk image fuzz testing (OPW)
Date: Mon, 26 May 2014 10:43:41 +0200 [thread overview]
Message-ID: <20140526084341.GA3813@noname.str.redhat.com> (raw)
In-Reply-To: <CALKf6DHUpaLrot8jzHR6whOuKzMC7i5AH_mZB2__xppbu_u4fw@mail.gmail.com>
Hi Maria,
Am 26.05.2014 um 07:07 hat M.Kustova geschrieben:
> My name is Maria and I'm a participant of the Outreach Program for Women.
> My project is fuzz testing of support of qcow2 image format.
>
> The project git:
> https://github.com/maxalab/qemu_fuzzer.git
>
> It's pubic, so welcome, make yourself at home.
Thanks for sharing this. I read your requirements file and have a
question or two.
The first is about what "actions" are. You define it as "structure
elements retrieved from an image format" or "element of an image
structure", which unfortunately doesn't make things much clearer to me.
My guess is that you mean a data structure (like header, L1 table,
refcount block, etc.) and this is the structure that is going to be
modified during the fuzzing? Is this right?
The other thing is that you seem to concentrate on generating test image
(and probably rightly so), but there's also the part that you need to
use that image for something, i.e. using the right actions with qemu to
actually test it against that image in a meaningful way (for example,
corrupting a snapshot's L1 table isn't interesting as long as this
snapshot isn't touched). What are your plans for determining what test
to run against the generated test images?
Also, if you don't mind, I'd like to be CCed on your further emails
about this project.
Kevin
next prev parent reply other threads:[~2014-05-26 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 5:07 [Qemu-devel] Disk image fuzz testing (OPW) M.Kustova
2014-05-26 8:43 ` Kevin Wolf [this message]
2014-05-26 9:53 ` M.Kustova
2014-05-26 9:24 ` Stefan Hajnoczi
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=20140526084341.GA3813@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=famz@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).