xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>
Subject: [PATCH 0/8] Fuzzing misc bugfix and performance improvements
Date: Mon, 20 Mar 2017 11:19:37 +0000	[thread overview]
Message-ID: <1490008785-6058-1-git-send-email-andrew.cooper3@citrix.com> (raw)

This series is a couple of bugfixes, but is mainly a set of performance
improvements to using the AFL test harness.  This series increases the
performance as reported by afl-fuzz from 6k execs/s to 38k execs/s, or more
than 6 times faster.

Andrew Cooper (8):
  tools/fuzz: Remove .d files in clean
  tools/fuzz: Use $(CC) for linking the harnesses
  tools/fuzz: Include LLVMFuzzerTestOneInput() in the generated .a
  tools/insn-fuzz: Use shorter filenames
  tools/insn-fuzz: Use getopt() for parsing the command line
  tools/insn-fuzz: Accept fuzzing input on stdin
  tools/insn-fuzz: Make use of LLVMFuzzerInitialize()
  tools/insn-fuzz: Support AFL's afl-clang-fast mode

 .gitignore                                         |   2 +-
 tools/fuzz/README.afl                              |  19 +++-
 tools/fuzz/libelf/Makefile                         |   5 +-
 tools/fuzz/x86_instruction_emulator/Makefile       |  19 ++--
 tools/fuzz/x86_instruction_emulator/afl-harness.c  | 114 +++++++++++++++++++++
 .../afl-x86-insn-emulator-fuzzer.c                 |  67 ------------
 .../{x86-insn-emulator-fuzzer.c => fuzz-emul.c}    |  19 ++--
 7 files changed, 154 insertions(+), 91 deletions(-)
 create mode 100644 tools/fuzz/x86_instruction_emulator/afl-harness.c
 delete mode 100644 tools/fuzz/x86_instruction_emulator/afl-x86-insn-emulator-fuzzer.c
 rename tools/fuzz/x86_instruction_emulator/{x86-insn-emulator-fuzzer.c => fuzz-emul.c} (99%)

-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2017-03-20 11:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 11:19 Andrew Cooper [this message]
2017-03-20 11:19 ` [PATCH 1/8] tools/fuzz: Remove .d files in clean Andrew Cooper
2017-03-20 11:19 ` [PATCH 2/8] tools/fuzz: Use $(CC) for linking the harnesses Andrew Cooper
2017-03-20 11:19 ` [PATCH 3/8] tools/fuzz: Include LLVMFuzzerTestOneInput() in the generated .a Andrew Cooper
2017-03-20 11:19 ` [PATCH 4/8] tools/insn-fuzz: Use shorter filenames Andrew Cooper
2017-03-20 11:19 ` [PATCH 5/8] tools/insn-fuzz: Use getopt() for parsing the command line Andrew Cooper
2017-03-20 11:19 ` [PATCH 6/8] tools/insn-fuzz: Accept fuzzing input on stdin Andrew Cooper
2017-03-20 11:19 ` [PATCH 7/8] tools/insn-fuzz: Make use of LLVMFuzzerInitialize() Andrew Cooper
2017-03-20 11:19 ` [PATCH 8/8] tools/insn-fuzz: Support AFL's afl-clang-fast mode Andrew Cooper
2017-03-20 15:55 ` [PATCH 0/8] Fuzzing misc bugfix and performance improvements Wei Liu

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=1490008785-6058-1-git-send-email-andrew.cooper3@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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).