public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <graf@amazon.com>
To: Sam Caccavale <samcacc@amazon.de>
Cc: <samcaccavale@gmail.com>, <nmanthey@amazon.de>,
	<wipawel@amazon.de>, <dwmw@amazon.co.uk>, <mpohlack@amazon.de>,
	<graf@amazon.de>, <karahmed@amazon.de>,
	<andrew.cooper3@citrix.com>, <JBeulich@suse.com>,
	<pbonzini@redhat.com>, <rkrcmar@redhat.com>, <tglx@linutronix.de>,
	<mingo@redhat.com>, <bp@alien8.de>, <hpa@zytor.com>,
	<paullangton4@gmail.com>, <anirudhkaushik@google.com>,
	<x86@kernel.org>, <kvm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [v2, 0/4] x86 instruction emulator fuzzing
Date: Fri, 21 Jun 2019 15:30:11 +0200	[thread overview]
Message-ID: <305788a1-afe8-add8-10ee-d738b76867bc@amazon.com> (raw)
In-Reply-To: <20190612153600.13073-1-samcacc@amazon.de>


On 12.06.19 17:35, Sam Caccavale wrote:
> Dear all,
>
> This series aims to provide an entrypoint for, and fuzz KVM's x86 instruction
> emulator from userspace.  It mirrors Xen's application of the AFL fuzzer to
> it's instruction emulator in the hopes of discovering vulnerabilities.
> Since this entrypoint also allows arbitrary execution of the emulators code
> from userspace, it may also be useful for testing.
>
> The current 4 patches build the emulator and 2 harnesses: simple-harness is
> an example of unit testing; afl-harness is a frontend for the AFL fuzzer.
>
> Patches
> =======
>
> - 01: Builds and links afl-harness with the required kernel objects.
> - 02: Introduces the minimal set of emulator operations and supporting code
> to emulate simple instructions.
> - 03: Demonstrates simple-harness as a unit test.
> - 04: Adds scripts for install, running, and crash triage.
>
> Any comments/suggestions are greatly appreciated.


The cover letter as well as the individual patches are missing a change 
log from v1 to v2.



Alex



      parent reply	other threads:[~2019-06-21 13:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 15:35 [v2, 0/4] x86 instruction emulator fuzzing Sam Caccavale
2019-06-12 15:35 ` [v2, 1/4] Build target for emulate.o as a userspace binary Sam Caccavale
2019-06-21 13:33   ` Alexander Graf
2019-06-12 15:35 ` [v2, 2/4] Emulate simple x86 instructions in userspace Sam Caccavale
2019-06-21 13:40   ` Alexander Graf
2019-06-12 15:35 ` [v2, 3/4] Demonstrating unit testing via simple-harness Sam Caccavale
2019-06-21 13:43   ` Alexander Graf
2019-06-12 15:36 ` [v2, 4/4] Added scripts for filtering, building, deploying Sam Caccavale
2019-06-21 13:50   ` Alexander Graf
2019-06-21 13:30 ` Alexander Graf [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=305788a1-afe8-add8-10ee-d738b76867bc@amazon.com \
    --to=graf@amazon.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anirudhkaushik@google.com \
    --cc=bp@alien8.de \
    --cc=dwmw@amazon.co.uk \
    --cc=graf@amazon.de \
    --cc=hpa@zytor.com \
    --cc=karahmed@amazon.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpohlack@amazon.de \
    --cc=nmanthey@amazon.de \
    --cc=paullangton4@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=samcacc@amazon.de \
    --cc=samcaccavale@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=wipawel@amazon.de \
    --cc=x86@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