linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sami Liedes <sami.liedes@iki.fi>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: 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 19:20:47 +0300	[thread overview]
Message-ID: <20120506162047.GF13332@sli.dy.fi> (raw)
In-Reply-To: <20120506102727.GA11619@amd.home.annexia.org>

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

On Sun, May 06, 2012 at 11:27:27AM +0100, Richard W.M. Jones wrote:
> 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].

I guess something like that could also be used for trying to generate
a small(ish) set of test case filesystem images that maximally
exercise the code.

> Anyway I was going to say: why not use libguestfs to provide a simpler
> framework for running KVM and the fuzzer?

I didn't even know about libguestfs. Very interesting; I need to take
a closer look at it.

I'd be glad quite glad if I could somehow get rid of the root
filesystem image, or to build and update it automatically. Right now
it's a headache for version control purposes.

	Sami

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

      reply	other threads:[~2012-05-06 16:20 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
2012-05-06 16:20   ` Sami Liedes [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=20120506162047.GF13332@sli.dy.fi \
    --to=sami.liedes@iki.fi \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rjones@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).