From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL v2 00/16] Block layer patches
Date: Thu, 22 Nov 2018 19:45:45 +0100 [thread overview]
Message-ID: <20181122184545.31487-1-kwolf@redhat.com> (raw)
The following changes since commit 47c1cc30e440860aa695358f7c2dd0b9d7b53d16:
Update version for v3.1.0-rc2 release (2018-11-20 18:10:26 +0000)
are available in the Git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to 6bd858b3117a5aab066f3cf02ca72000eaa10ddb:
block: Update BlockDriverState.inherits_from on bdrv_drop_intermediate() (2018-11-22 19:37:31 +0100)
----------------------------------------------------------------
Block layer patches:
- block: Fix update of BDRV_O_AUTO_RDONLY in update_flags_from_options()
- block: Fix option inheritance after stream/commit job graph changes
- qemu-img: Fix memory leak and typo in error message
- nvme: Fixes for lockups and crashes
- scsi-disk: Fix crash if underlying host file or disk returns error
- Several qemu-iotests fixes and improvements
----------------------------------------------------------------
Alberto Garcia (3):
block: Fix update of BDRV_O_AUTO_RDONLY in update_flags_from_options()
block: Update BlockDriverState.inherits_from on bdrv_set_backing_hd()
block: Update BlockDriverState.inherits_from on bdrv_drop_intermediate()
Daniel P. Berrangé (1):
iotests: fix nbd test 233 to work correctly with raw images
Eric Blake (2):
iotests: Skip 233 if certtool not installed
iotests: Enhance 223 to cover multiple bitmap granularities
Igor Druzhinin (1):
nvme: call blk_drain in NVMe reset code to avoid lockups
Kevin Wolf (3):
iotests: Replace time.clock() with Timeout
iotests: Replace assertEquals() with assertEqual()
Revert "nvme: fix oob access issue(CVE-2018-16847)"
Logan Gunthorpe (1):
nvme: fix bug with PCI IRQ pins on teardown
Max Reitz (2):
qemu-img: Fix typo
qemu-img: Fix leak
Paolo Bonzini (2):
nvme: fix out-of-bounds access to the CMB
nvme: fix CMB endianness confusion
Richard W.M. Jones (1):
scsi-disk: Fix crash if underlying host file or disk returns error
block.c | 41 ++++++++++++-
hw/block/nvme.c | 19 ++----
hw/scsi/scsi-disk.c | 2 +-
qemu-img.c | 3 +-
tests/nvme-test.c | 68 ++++++++++++++++++---
tests/Makefile.include | 2 +-
tests/qemu-iotests/041 | 6 +-
tests/qemu-iotests/118 | 20 +++---
tests/qemu-iotests/161 | 137 ++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/161.out | 39 ++++++++++++
tests/qemu-iotests/223 | 43 ++++++++++---
tests/qemu-iotests/223.out | 32 +++++++---
tests/qemu-iotests/233 | 9 ++-
tests/qemu-iotests/common.tls | 3 +
tests/qemu-iotests/group | 1 +
tests/qemu-iotests/iotests.py | 2 +-
16 files changed, 364 insertions(+), 63 deletions(-)
create mode 100755 tests/qemu-iotests/161
create mode 100644 tests/qemu-iotests/161.out
next reply other threads:[~2018-11-22 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 18:45 Kevin Wolf [this message]
2018-11-23 9:42 ` [Qemu-devel] [PULL v2 00/16] Block layer 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=20181122184545.31487-1-kwolf@redhat.com \
--to=kwolf@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).