From: Thomas Huth <thuth@redhat.com>
To: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [PULL 00/10] qtest / fuzzer patches
Date: Tue, 21 Jul 2020 10:10:45 +0200 [thread overview]
Message-ID: <20200721081055.14073-1-thuth@redhat.com> (raw)
Hi Peter,
the following changes since commit af3d69058e09bede9900f266a618ed11f76f49f3:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20200720' into staging (2020-07-20 15:58:07 +0100)
are available in the Git repository at:
https://gitlab.com/huth/qemu.git tags/pull-request-2020-07-21
for you to fetch changes up to 7ad36e2e241bd924f774a1f9fb208c102da58e50:
hw: Mark nd_table[] misuse in realize methods FIXME (2020-07-21 08:41:15 +0200)
----------------------------------------------------------------
* Fix memory leak in fuzzer
* Fuzzer documentation updates
* Some other minor fuzzer updates
* Fix "make check-qtest SPEED=slow" (bug in msf2 instance_init)
----------------------------------------------------------------
Alexander Bulekov (6):
fuzz: Fix leak when assembling datadir path string
gitlab-ci.yml: Add oss-fuzz build tests
fuzz: build without AddressSanitizer, by default
docs/fuzz: describe building fuzzers with enable-sanitizers
docs/fuzz: add information about useful libFuzzer flags
docs/fuzz: add instructions for generating a coverage report
Markus Armbruster (2):
msf2: Unbreak device-list-properties for "msf-soc"
hw: Mark nd_table[] misuse in realize methods FIXME
Thomas Huth (2):
scripts/oss-fuzz: Limit target list to i386-softmmu
MAINTAINERS: Extend the device fuzzing section
.gitlab-ci.yml | 22 ++++++++---------
MAINTAINERS | 2 ++
configure | 10 ++++----
docs/devel/fuzzing.txt | 63 +++++++++++++++++++++++++++++++++++++++++++++--
hw/arm/allwinner-h3.c | 1 +
hw/arm/msf2-soc.c | 9 ++++---
hw/arm/xlnx-versal.c | 1 +
hw/arm/xlnx-zynqmp.c | 1 +
hw/dma/sparc32_dma.c | 1 +
hw/riscv/sifive_u.c | 1 +
scripts/oss-fuzz/build.sh | 2 +-
tests/qtest/fuzz/fuzz.c | 12 +++++----
12 files changed, 96 insertions(+), 29 deletions(-)
next reply other threads:[~2020-07-21 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 8:10 Thomas Huth [this message]
2020-07-21 8:10 ` [PULL 01/10] scripts/oss-fuzz: Limit target list to i386-softmmu Thomas Huth
2020-07-21 8:10 ` [PULL 02/10] fuzz: Fix leak when assembling datadir path string Thomas Huth
2020-07-21 8:10 ` [PULL 03/10] gitlab-ci.yml: Add oss-fuzz build tests Thomas Huth
2020-07-21 8:10 ` [PULL 04/10] fuzz: build without AddressSanitizer, by default Thomas Huth
2020-07-21 8:10 ` [PULL 05/10] docs/fuzz: describe building fuzzers with enable-sanitizers Thomas Huth
2020-07-21 8:10 ` [PULL 06/10] docs/fuzz: add information about useful libFuzzer flags Thomas Huth
2020-07-21 8:10 ` [PULL 07/10] docs/fuzz: add instructions for generating a coverage report Thomas Huth
2020-07-21 8:10 ` [PULL 08/10] MAINTAINERS: Extend the device fuzzing section Thomas Huth
2020-07-21 8:10 ` [PULL 09/10] msf2: Unbreak device-list-properties for "msf-soc" Thomas Huth
2020-07-21 8:10 ` [PULL 10/10] hw: Mark nd_table[] misuse in realize methods FIXME Thomas Huth
2020-07-21 13:03 ` [PULL 00/10] qtest / fuzzer patches Peter Maydell
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=20200721081055.14073-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).