qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL 0/7] Block patches for 3.0-rc0
Date: Mon,  9 Jul 2018 20:58:21 +0200	[thread overview]
Message-ID: <20180709185828.4248-1-mreitz@redhat.com> (raw)

The following changes since commit ec7eb2ae77cc207064e17ace048f7ec0c4b85d6f:

  translate-all: honour CF_NOCACHE in tb_gen_code (2018-07-09 16:14:36 +0100)

are available in the Git repository at:

  https://git.xanclic.moe/XanClic/qemu.git tags/pull-block-2018-07-09

for you to fetch changes up to 0e4e4318eaa56c831001bdf617094807ec6d451c:

  qcow2: add overlap check for bitmap directory (2018-07-09 19:43:24 +0200)

----------------------------------------------------------------
Block patches for 3.0-rc0:
- qcow2 metadata overlap protection for the persistent bitmap directory
- Various bug fixes

----------------------------------------------------------------
Fam Zheng (4):
  qcow2: Drop unused cluster_data
  file-posix: Fix fd_open check in raw_co_copy_range_to
  qcow2: Drop unreachable break
  raw: Drop superfluous semicolon

Max Reitz (2):
  vmdk: Fix possible segfault with non-VMDK backing
  iotests: Add VMDK backing file correlation test

Vladimir Sementsov-Ogievskiy (1):
  qcow2: add overlap check for bitmap directory

 qapi/block-core.json       |  21 +++---
 block/qcow2.h              |  45 +++++++------
 block/file-posix.c         |   2 +-
 block/qcow2-bitmap.c       |   7 +-
 block/qcow2-refcount.c     |  10 +++
 block/qcow2.c              |  25 +++----
 block/raw-format.c         |   2 +-
 block/vmdk.c               |   6 ++
 tests/qemu-iotests/225     | 132 +++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/225.out |  24 +++++++
 tests/qemu-iotests/group   |   1 +
 11 files changed, 231 insertions(+), 44 deletions(-)
 create mode 100755 tests/qemu-iotests/225
 create mode 100644 tests/qemu-iotests/225.out

-- 
2.17.1

             reply	other threads:[~2018-07-09 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 18:58 Max Reitz [this message]
2018-07-09 18:58 ` [Qemu-devel] [PULL 1/7] qcow2: Drop unused cluster_data Max Reitz
2018-07-09 18:58 ` [Qemu-devel] [PULL 2/7] file-posix: Fix fd_open check in raw_co_copy_range_to Max Reitz
2018-07-09 18:58 ` [Qemu-devel] [PULL 3/7] qcow2: Drop unreachable break Max Reitz
2018-07-09 18:58 ` [Qemu-devel] [PULL 4/7] raw: Drop superfluous semicolon Max Reitz
2018-07-09 18:58 ` [Qemu-devel] [PULL 5/7] vmdk: Fix possible segfault with non-VMDK backing Max Reitz
2018-07-09 18:58 ` [Qemu-devel] [PULL 6/7] iotests: Add VMDK backing file correlation test Max Reitz
2018-07-09 18:58 ` [Qemu-devel] [PULL 7/7] qcow2: add overlap check for bitmap directory Max Reitz
2018-07-10  9:01 ` [Qemu-devel] [PULL 0/7] Block patches for 3.0-rc0 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=20180709185828.4248-1-mreitz@redhat.com \
    --to=mreitz@redhat.com \
    --cc=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).