From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <jbeulich@suse.com>
Subject: [PATCH 0/4] fuzz: basic AFL support
Date: Fri, 20 Jan 2017 12:11:03 +0000 [thread overview]
Message-ID: <1484914267-8942-1-git-send-email-wei.liu2@citrix.com> (raw)
Provide simple stub programs for AFL fuzzer. For usage, please see README.afl.
This series doesn't aim to improve fuzzing targets. It is just demonstration
for how we could use the same fuzzing code for both oss-fuzz and AFL.
The stub programs are identical in libefl and x86 emulator at the moment, but
they will likely diverge in the future. The duplication of code is deliberate.
Julien, FYI I think the in-tree libfdt could have something similar, too.
Wei.
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Julien Grall <julien.grall@arm.com>
Wei Liu (4):
tools/fuzz: add missing dependency in x86 insn fuzzer build rule
tools/fuzz: add AFL stub program for x86 insn emulator fuzzer
tools/fuzz: add AFL stub program for libefl fuzzer
tools/fuzz: add README.afl
.gitignore | 2 ++
tools/fuzz/README.afl | 27 ++++++++++++++
tools/fuzz/{README => README.oss-fuzz} | 0
tools/fuzz/libelf/Makefile | 7 +++-
tools/fuzz/libelf/afl-libelf-fuzzer.c | 42 ++++++++++++++++++++++
tools/fuzz/x86_instruction_emulator/Makefile | 11 ++++--
.../afl-x86-insn-emulator-fuzzer.c | 42 ++++++++++++++++++++++
7 files changed, 128 insertions(+), 3 deletions(-)
create mode 100644 tools/fuzz/README.afl
rename tools/fuzz/{README => README.oss-fuzz} (100%)
create mode 100644 tools/fuzz/libelf/afl-libelf-fuzzer.c
create mode 100644 tools/fuzz/x86_instruction_emulator/afl-x86-insn-emulator-fuzzer.c
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-01-20 12:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 12:11 Wei Liu [this message]
2017-01-20 12:11 ` [PATCH 1/4] tools/fuzz: add missing dependency in x86 insn fuzzer build rule Wei Liu
2017-01-20 12:11 ` [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer Wei Liu
2017-01-24 10:09 ` Jan Beulich
2017-01-24 16:43 ` Wei Liu
2017-01-24 17:05 ` Ian Jackson
2017-01-24 17:18 ` Wei Liu
2017-01-24 17:22 ` Ian Jackson
2017-01-24 17:25 ` Andrew Cooper
2017-01-24 17:27 ` Wei Liu
2017-01-24 17:30 ` Ian Jackson
2017-01-24 17:37 ` Wei Liu
2017-01-24 17:46 ` Ian Jackson
2017-01-24 17:28 ` Wei Liu
2017-01-20 12:11 ` [PATCH 3/4] tools/fuzz: add AFL stub program for libefl fuzzer Wei Liu
2017-01-24 10:10 ` Jan Beulich
2017-01-20 12:11 ` [PATCH 4/4] tools/fuzz: add README.afl Wei Liu
2017-01-24 19:27 ` Andrew Cooper
2017-01-25 9:49 ` Wei Liu
2017-01-25 9:51 ` George Dunlap
2017-01-25 9:54 ` Wei Liu
2017-01-24 18:18 ` [PATCH 0/4] fuzz: basic AFL support Julien Grall
2017-01-24 18:56 ` Wei Liu
2017-01-24 19:00 ` Stefano Stabellini
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=1484914267-8942-1-git-send-email-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xenproject.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).