From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: Request for help: Help integrating Xen into Google oss-fuzz
Date: Thu, 5 Jan 2017 15:59:45 +0000 [thread overview]
Message-ID: <20170105155945.GG27743@citrix.com> (raw)
Hi all
Oss-fuzz [0] is a continuous fuzzing service for open source
software. During last release cycle we put in a lot of effort to fuzz
Xen, so it would make sense to try to run it in oss-fuzz.
We've already committed two fuzzing targets (x86 emulator and libelf,
both of which happen to get a lot of changes recently) in
xen.git. We're still missing some shell scripts and a dockerfile to
integrate those targets into oss-fuzz (example [1]).
Would anyone be interested in such task? Drop me a private email if
you're interested in helping. We would need to discuss the interface
between Xen build system and the scripts.
Regards,
Wei.
[0] https://github.com/google/oss-fuzz
[1] https://github.com/google/oss-fuzz/tree/master/projects/expat
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-01-05 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 15:59 Wei Liu [this message]
2017-01-18 11:43 ` Request for help: Help integrating Xen into Google oss-fuzz 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=20170105155945.GG27743@citrix.com \
--to=wei.liu2@citrix.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).