From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PULL 00/11] Block patches
Date: Tue, 5 Nov 2019 16:43:21 +0100 [thread overview]
Message-ID: <20191105154332.181417-1-stefanha@redhat.com> (raw)
The following changes since commit 36609b4fa36f0ac934874371874416f7533a5408:
Merge remote-tracking branch 'remotes/palmer/tags/palmer-for-master-4.2-sf1' into staging (2019-11-02 17:59:03 +0000)
are available in the Git repository at:
https://github.com/stefanha/qemu.git tags/block-pull-request
for you to fetch changes up to 9fdd7860adec188ed50d2530e9a819e8d953f9bb:
image-fuzzer: Use OSerror.strerror instead of tuple subscript (2019-11-05 16:36:11 +0100)
----------------------------------------------------------------
Pull request
Let's get the image fuzzer Python 3 changes merged in QEMU 4.2.
----------------------------------------------------------------
Eduardo Habkost (11):
image-fuzzer: Open image files in binary mode
image-fuzzer: Write bytes instead of string to image file
image-fuzzer: Explicitly use integer division operator
image-fuzzer: Use io.StringIO
image-fuzzer: Use %r for all fiels at Field.__repr__()
image-fuzzer: Return bytes objects on string fuzzing functions
image-fuzzer: Use bytes constant for field values
image-fuzzer: Encode file name and file format to bytes
image-fuzzer: Run using python3
image-fuzzer: Use errors parameter of subprocess.Popen()
image-fuzzer: Use OSerror.strerror instead of tuple subscript
tests/image-fuzzer/qcow2/__init__.py | 1 -
tests/image-fuzzer/qcow2/fuzz.py | 54 +++++++++++++-------------
tests/image-fuzzer/qcow2/layout.py | 57 ++++++++++++++--------------
tests/image-fuzzer/runner.py | 16 ++++----
4 files changed, 63 insertions(+), 65 deletions(-)
--
2.23.0
next reply other threads:[~2019-11-05 15:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 15:43 Stefan Hajnoczi [this message]
2019-11-05 15:43 ` [PULL 01/11] image-fuzzer: Open image files in binary mode Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 02/11] image-fuzzer: Write bytes instead of string to image file Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 03/11] image-fuzzer: Explicitly use integer division operator Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 04/11] image-fuzzer: Use io.StringIO Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 05/11] image-fuzzer: Use %r for all fiels at Field.__repr__() Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 06/11] image-fuzzer: Return bytes objects on string fuzzing functions Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 07/11] image-fuzzer: Use bytes constant for field values Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 08/11] image-fuzzer: Encode file name and file format to bytes Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 09/11] image-fuzzer: Run using python3 Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 10/11] image-fuzzer: Use errors parameter of subprocess.Popen() Stefan Hajnoczi
2019-11-05 15:43 ` [PULL 11/11] image-fuzzer: Use OSerror.strerror instead of tuple subscript Stefan Hajnoczi
2019-11-06 16:01 ` [PULL 00/11] Block patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-06-05 9:47 Stefan Hajnoczi
2020-06-05 12:52 ` Peter Maydell
2021-09-07 8:13 Stefan Hajnoczi
2021-09-07 15:08 ` 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=20191105154332.181417-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.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).