From: "Richard W.M. Jones" <rjones@redhat.com>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Announcing the Berserker toolkit for (semi-)automated fs fuzz testing
Date: Sun, 6 May 2012 11:27:27 +0100 [thread overview]
Message-ID: <20120506102727.GA11619@amd.home.annexia.org> (raw)
In-Reply-To: <20120428013904.GE20648@sli.dy.fi>
On Sat, Apr 28, 2012 at 04:39:04AM +0300, Sami Liedes wrote:
> This is an announcement of the first release of the Berserker toolkit
> for (semi-)automated fuzz testing and testcase minimization of Linux
> kernel filesystem implementations.
This looks interesting, and it's very necessary to find these bugs in
filesystem drivers to improve the security around virtualization and
untrusted disk images.
I wrote something similar a while back, trying to use systemtap to do
feedback-directed fuzz testing. By putting a tracepoint on every line
in the filesystem module, you can find out how many lines of code are
actually executed when mounting/using the fuzzed filesystem and use
that as a cost function for feedback (maximizing the # of lines
executed, rather than blindly fuzzing). Unfortunately it doesn't work
yet because of a bug in Linux[1].
Anyway I was going to say: why not use libguestfs to provide a simpler
framework for running KVM and the fuzzer?
Rich.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=713248
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2012-05-06 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 1:39 Announcing the Berserker toolkit for (semi-)automated fs fuzz testing Sami Liedes
2012-05-06 10:27 ` Richard W.M. Jones [this message]
2012-05-06 16:20 ` Sami Liedes
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=20120506102727.GA11619@amd.home.annexia.org \
--to=rjones@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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).