qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] Fuzzing event loops
Date: Mon, 26 Jun 2017 16:53:45 -0400	[thread overview]
Message-ID: <71215f3b-4b44-accc-d84a-87d4749bf391@redhat.com> (raw)
In-Reply-To: <CAJSP0QUD58kjc=8WAxwocK_HGJGqG-YeR5LqU3cCZCgdemZe4g@mail.gmail.com>



On 06/11/2017 06:47 AM, Stefan Hajnoczi wrote:
> I wanted to share this idea about fuzzing event loops:
> 
> https://blog.acolyer.org/2017/06/09/node-fz-fuzzing-the-server-side-event-driven-architecture/
> 
> The idea is to expose ordering dependencies and atomicity bugs in
> event loop callbacks/coroutines by randomly shuffling the order in
> which fd handlers, timers, etc execute.
> 
> I'm not sure we'd find many bugs since QEMU tends to use big locks or
> request serialization when concurrency gets tricky in the block layer.
> Still, it's an interesting concept that we could apply in the future.
> 
> Stefan
> 

Sounds fun, probably too detailed for a GSoC/Outreachy project, right?
Do we have a page on the wiki for random "Hey, this might be nice..." ideas?

(Or is that a bad idea itself so we don't have a graveyard of 'not my
problem' projects?)

--js

  reply	other threads:[~2017-06-26 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-11 10:47 [Qemu-devel] Fuzzing event loops Stefan Hajnoczi
2017-06-26 20:53 ` John Snow [this message]
2017-07-05 12:47   ` [Qemu-devel] [Qemu-block] " 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=71215f3b-4b44-accc-d84a-87d4749bf391@redhat.com \
    --to=jsnow@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).