[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] 611e06: replication: Fix replication open fai
|
From: |
GitHub |
|
Subject: |
[Qemu-commits] [qemu/qemu] 611e06: replication: Fix replication open fail |
|
Date: |
Fri, 17 Nov 2017 12:29:18 -0800 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: 611e0653adfb2765b712ad8bd312f2fd9765d13c
https://github.com/qemu/qemu/commit/611e0653adfb2765b712ad8bd312f2fd9765d13c
Author: Wang Guang <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/replication.c
Log Message:
-----------
replication: Fix replication open fail
replication_child_perm request write
permissions for all child which will lead bdrv_check_perm fail.
replication_child_perm() should request write
permissions only if it is writable itself.
Signed-off-by: Wang Guang <address@hidden>
Signed-off-by: Wang Yong <address@hidden>
Reviewed-by: Xie Changlong <address@hidden>
Signed-off-by: Kevin Wolf <address@hidden>
Commit: c60f6fcfbddccbafc80ae4b3d087406eb7182c3a
https://github.com/qemu/qemu/commit/c60f6fcfbddccbafc80ae4b3d087406eb7182c3a
Author: Kevin Wolf <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M tests/qemu-iotests/182
Log Message:
-----------
qemu-iotests: Use -nographic in 182
This avoids that random UI frontend error messages end up in the output.
In particular, we were seeing this line in CI error logs:
+Unable to init server: Could not connect: Connection refused
Signed-off-by: Kevin Wolf <address@hidden>
Reviewed-by: Kashyap Chamarthy <address@hidden>
Reviewed-by: Jeff Cody <address@hidden>
Commit: 6473069416ddbb0ef4dccca9bffe87c1424f45fa
https://github.com/qemu/qemu/commit/6473069416ddbb0ef4dccca9bffe87c1424f45fa
Author: Kevin Wolf <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block.c
Log Message:
-----------
block: Fix error path in bdrv_backing_update_filename()
error_setg_errno() takes a positive errno code. Spotted by Coverity
(CID 1381628).
Signed-off-by: Kevin Wolf <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Stefan Hajnoczi <address@hidden>
Commit: f66afbe26f0c093d639610d70d16d7cc3183b652
https://github.com/qemu/qemu/commit/f66afbe26f0c093d639610d70d16d7cc3183b652
Author: Daniel P. Berrange <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2.c
Log Message:
-----------
qcow2: don't permit changing encryption parameters
Currently if trying to change encryption parameters on a qcow2 image, qemu-img
will abort. We already explicitly check for attempt to change encrypt.format
but missed other parameters like encrypt.key-secret. Rather than list each
parameter, just blacklist changing of all parameters with a 'encrypt.' prefix.
Signed-off-by: Daniel P. Berrange <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Kevin Wolf <address@hidden>
Commit: 398e6ad014df261d20d3fd6cff2cfbf940bac714
https://github.com/qemu/qemu/commit/398e6ad014df261d20d3fd6cff2cfbf940bac714
Author: Kevin Wolf <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block.c
M block/bochs.c
M block/cloop.c
M block/dmg.c
M block/rbd.c
M block/vvfat.c
M qapi/block-core.json
Log Message:
-----------
block: Deprecate bdrv_set_read_only() and users
bdrv_set_read_only() is used by some block drivers to override the
read-only option given by the user. This is not how read-only images
generally work in QEMU: Instead of second guessing what the user really
meant (which currently includes making an image read-only even if the
user didn't only use the default, but explicitly said read-only=off), we
should error out if we can't provide what the user requested.
This adds deprecation warnings to all callers of bdrv_set_read_only() so
that the behaviour can be corrected after the usual deprecation period.
Signed-off-by: Kevin Wolf <address@hidden>
Commit: f06033295b51d4868c2b4921ad2287e8f55eb688
https://github.com/qemu/qemu/commit/f06033295b51d4868c2b4921ad2287e8f55eb688
Author: Daniel P. Berrange <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2.c
A tests/qemu-iotests/198
A tests/qemu-iotests/198.out
M tests/qemu-iotests/common.filter
M tests/qemu-iotests/group
Log Message:
-----------
qcow2: fix image corruption after committing qcow2 image into base
After committing the qcow2 image contents into the base image, qemu-img
will call bdrv_make_empty to drop the payload in the layered image.
When this is done for qcow2 images, it blows away the LUKS encryption
header, making the resulting image unusable. There are two codepaths
for emptying a qcow2 image, and the second (slower) codepath leaves
the LUKS header intact, so force use of that codepath.
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Daniel P. Berrange <address@hidden>
Signed-off-by: Kevin Wolf <address@hidden>
Commit: dafe096057373d95847e1c99c2fece34be9fc5bb
https://github.com/qemu/qemu/commit/dafe096057373d95847e1c99c2fece34be9fc5bb
Author: Kevin Wolf <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block.c
Log Message:
-----------
block: Fix permissions in image activation
Inactive images generally request less permissions for their image files
than they would if they were active (in particular, write permissions).
Activating the image involves extending the permissions, therefore.
drv->bdrv_invalidate_cache() can already require write access to the
image file, so we have to update the permissions earlier than that.
The current code does it only later, so we have to move up this part.
Signed-off-by: Kevin Wolf <address@hidden>
Reviewed-by: Max Reitz <address@hidden>
Commit: 3590cd0f045a5ba8ab40815ba887cbb2b71f0af9
https://github.com/qemu/qemu/commit/3590cd0f045a5ba8ab40815ba887cbb2b71f0af9
Author: Vladimir Sementsov-Ogievskiy <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
A tests/qemu-iotests/196
A tests/qemu-iotests/196.out
M tests/qemu-iotests/group
Log Message:
-----------
iotests: test clearing unknown autoclear_features by qcow2
Test clearing unknown autoclear_features by qcow2 on incoming
migration.
[ kwolf: Fixed wait for destination VM startup ]
Signed-off-by: Vladimir Sementsov-Ogievskiy <address@hidden>
Signed-off-by: Kevin Wolf <address@hidden>
Reviewed-by: Max Reitz <address@hidden>
Commit: 4096974e1885913dfe2931863be47bd35b266521
https://github.com/qemu/qemu/commit/4096974e1885913dfe2931863be47bd35b266521
Author: Eric Blake <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2.c
M tests/qemu-iotests/176
M tests/qemu-iotests/176.out
Log Message:
-----------
qcow2: fix image corruption on commit with persistent bitmap
If an image contains persistent bitmaps, we cannot use the
fast path of bdrv_make_empty() to clear the image during
qemu-img commit, because that will lose the clusters related
to the bitmaps.
Also leave a comment in qcow2_read_extensions to remind future
feature additions to think about fast-path removal, since we
just barely fixed the same bug for LUKS encryption.
It's a pain that qemu-img has not yet been taught to manipulate,
or even at a very minimum display, information about persistent
bitmaps; instead, we have to use QMP commands. It's also a
pain that only qeury-block and x-debug-block-dirty-bitmap-sha256
will allow bitmap introspection; but the former requires the
node to be hooked to a block device, and the latter is experimental.
Signed-off-by: Eric Blake <address@hidden>
Signed-off-by: Kevin Wolf <address@hidden>
Commit: 84be629d5545b5ccc5bff2824e4288677e27de9c
https://github.com/qemu/qemu/commit/84be629d5545b5ccc5bff2824e4288677e27de9c
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M include/qapi/qmp/qdict.h
A include/qapi/qmp/qnull.h
M include/qapi/qmp/qobject.h
M include/qapi/qmp/types.h
M qapi/qapi-clone-visitor.c
M qapi/string-input-visitor.c
M qobject/qnull.c
M tests/check-qnull.c
Log Message:
-----------
qapi/qnull: Add own header
Signed-off-by: Max Reitz <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Reviewed-by: Markus Armbruster <address@hidden>
Message-id: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Commit: 254bf807e5354c7b424d6fc28cb17c4f9ba43e35
https://github.com/qemu/qemu/commit/254bf807e5354c7b424d6fc28cb17c4f9ba43e35
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M include/qapi/qmp/qlist.h
M scripts/coccinelle/qobject.cocci
Log Message:
-----------
qapi/qlist: Add qlist_append_null() macro
Besides the macro itself, this patch also adds a corresponding
Coccinelle rule.
Signed-off-by: Max Reitz <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Message-id: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Commit: b38dd678a21582e03ecd2dec76ccf8290455628a
https://github.com/qemu/qemu/commit/b38dd678a21582e03ecd2dec76ccf8290455628a
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M include/qapi/qmp/qbool.h
M include/qapi/qmp/qdict.h
M include/qapi/qmp/qlist.h
M include/qapi/qmp/qnull.h
M include/qapi/qmp/qnum.h
M include/qapi/qmp/qobject.h
M include/qapi/qmp/qstring.h
M qobject/qbool.c
M qobject/qdict.c
M qobject/qlist.c
M qobject/qnull.c
M qobject/qnum.c
M qobject/qobject.c
M qobject/qstring.c
Log Message:
-----------
qapi: Add qobject_is_equal()
This generic function (along with its implementations for different
types) determines whether two QObjects are equal.
Signed-off-by: Max Reitz <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Reviewed-by: Markus Armbruster <address@hidden>
Message-id: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Commit: 54fd1b0d260cf9615d3385c93702277e81f0b639
https://github.com/qemu/qemu/commit/54fd1b0d260cf9615d3385c93702277e81f0b639
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block.c
Log Message:
-----------
block: qobject_is_equal() in bdrv_reopen_prepare()
Currently, bdrv_reopen_prepare() assumes that all BDS options are
strings. However, this is not the case if the BDS has been created
through the json: pseudo-protocol or blockdev-add.
Note that the user-invokable reopen command is an HMP command, so you
can only specify strings there. Therefore, specifying a non-string
option with the "same" value as it was when originally created will now
return an error because the values are supposedly similar (and there is
no way for the user to circumvent this but to just not specify the
option again -- however, this is still strictly better than just
crashing).
Signed-off-by: Max Reitz <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Message-id: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Commit: 791cbccc9422f17ff907f33d5a689d88b8610cff
https://github.com/qemu/qemu/commit/791cbccc9422f17ff907f33d5a689d88b8610cff
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M tests/qemu-iotests/133
M tests/qemu-iotests/133.out
Log Message:
-----------
iotests: Add test for non-string option reopening
Signed-off-by: Max Reitz <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Message-id: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Commit: 1b76e8389b2cba75e158488f0f6fb72a04f36b1d
https://github.com/qemu/qemu/commit/1b76e8389b2cba75e158488f0f6fb72a04f36b1d
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M tests/.gitignore
M tests/Makefile.include
A tests/check-qobject.c
Log Message:
-----------
tests: Add check-qobject for equality tests
Add a new test file (check-qobject.c) for unit tests that concern
QObjects as a whole.
Its only purpose for now is to test the qobject_is_equal() function.
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: 2b7731938d9279a77d2df62fd9641afc00adbc7c
https://github.com/qemu/qemu/commit/2b7731938d9279a77d2df62fd9641afc00adbc7c
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M tests/qemu-iotests/020
M tests/qemu-iotests/020.out
Log Message:
-----------
iotests: Add test for failing qemu-img commit
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: 3e3b838ffeba42eced87595b0a23dc38f7c0c21b
https://github.com/qemu/qemu/commit/3e3b838ffeba42eced87595b0a23dc38f7c0c21b
Author: Anton Nefedov <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2.c
Log Message:
-----------
qcow2: reject unaligned offsets in write compressed
Misaligned compressed write is not supported.
Signed-off-by: Anton Nefedov <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: 791fff504cad4d935dfaab6333ff9b7d95cbfe3f
https://github.com/qemu/qemu/commit/791fff504cad4d935dfaab6333ff9b7d95cbfe3f
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2.c
M tests/qemu-iotests/060
M tests/qemu-iotests/060.out
Log Message:
-----------
qcow2: check_errors are fatal
When trying to repair a dirty image, qcow2_check() may apparently
succeed (no really fatal error occurred that would prevent the check
from continuing), but if check_errors in the result object is non-zero,
we cannot trust the image to be usable.
Reported-by: R. Nageswara Sastry <address@hidden>
Buglink: https://bugs.launchpad.net/qemu/+bug/1728639
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: 93bbaf03ff7fd490e823814b8f5d6849a7b71a64
https://github.com/qemu/qemu/commit/93bbaf03ff7fd490e823814b8f5d6849a7b71a64
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2-cluster.c
M tests/qemu-iotests/060
M tests/qemu-iotests/060.out
Log Message:
-----------
qcow2: Unaligned zero cluster in handle_alloc()
We should check whether the cluster offset we are about to use is
actually valid; that is, whether it is aligned to cluster boundaries.
Reported-by: R. Nageswara Sastry <address@hidden>
Buglink: https://bugs.launchpad.net/qemu/+bug/1728643
Buglink: https://bugs.launchpad.net/qemu/+bug/1728657
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: d470ad42acfc73c45d3e8ed5311a491160b4c100
https://github.com/qemu/qemu/commit/d470ad42acfc73c45d3e8ed5311a491160b4c100
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block.c
M block/io.c
M block/qapi.c
M block/replication.c
M block/vvfat.c
M tests/qemu-iotests/060
M tests/qemu-iotests/060.out
Log Message:
-----------
block: Guard against NULL bs->drv
We currently do not guard everywhere against a NULL bs->drv where we
should be doing so. Most of the places fixed here just do not care
about that case at all.
Some care implicitly, e.g. through a prior function call to
bdrv_getlength() which would always fail for an ejected BDS. Add an
assert there to make it more obvious.
Other places seem to care, but do so insufficiently: Freeing clusters in
a qcow2 image is an error-free operation, but it may leave the image in
an unusable state anyway. Giving qcow2_free_clusters() an error code is
not really viable, it is much easier to note that bs->drv may be NULL
even after a successful driver call. This concerns bdrv_co_flush(), and
the way the check is added to bdrv_co_pdiscard() (in every iteration
instead of only once).
Finally, some places employ at least an assert(bs->drv); somewhere, that
may be reasonable (such as in the reopen code), but in
bdrv_has_zero_init(), it is definitely not. Returning 0 there in case
of an ejected BDS saves us much headache instead.
Reported-by: R. Nageswara Sastry <address@hidden>
Buglink: https://bugs.launchpad.net/qemu/+bug/1728660
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: 23482f8a603a7fc591b770c94ff75651a7da88b2
https://github.com/qemu/qemu/commit/23482f8a603a7fc591b770c94ff75651a7da88b2
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2-refcount.c
M block/qcow2.h
M tests/qemu-iotests/060
M tests/qemu-iotests/060.out
Log Message:
-----------
qcow2: Add bounds check to get_refblock_offset()
Reported-by: R. Nageswara Sastry <address@hidden>
Buglink: https://bugs.launchpad.net/qemu/+bug/1728661
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: 4efb1f7c612ff35badc8f8cbda78ac891fabf20a
https://github.com/qemu/qemu/commit/4efb1f7c612ff35badc8f8cbda78ac891fabf20a
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2-cache.c
M tests/qemu-iotests/060
M tests/qemu-iotests/060.out
Log Message:
-----------
qcow2: Refuse to get unaligned offsets from cache
Instead of using an assertion, it is better to emit a corruption event
here. Checking all offsets for correct alignment can be tedious and it
is easily possible to forget to do so. qcow2_cache_do_get() is a
function every L2 and refblock access has to go through, so this is a
good central point to add such a check.
And for good measure, let us also add an assertion that the offset is
non-zero. Making this a corruption event is not feasible, because a
zero offset usually means something special (such as the cluster is
unused), so all callers should be checking this anyway. If they do not,
it is their fault, hence the assertion here.
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: 08546bcfb260c28141e27cf3367c443528602fc0
https://github.com/qemu/qemu/commit/08546bcfb260c28141e27cf3367c443528602fc0
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block/qcow2-cache.c
Log Message:
-----------
qcow2: Fix overly broad madvise()
@mem_size and @offset are both size_t, thus subtracting them from one
another will just return a big size_t if mem_size < offset -- even more
obvious here because the result is stored in another size_t.
Checking that result to be positive is therefore not sufficient to
exclude the case that offset > mem_size. Thus, we currently sometimes
issue an madvise() over a very large address range.
This is triggered by iotest 163, but with -m64, this does not result in
tangible problems. But with -m32, this test produces three segfaults,
all of which are fixed by this patch.
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Alberto Garcia <address@hidden>
Reviewed-by: Darren Kenny <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: 5e003f17ec518cd96f5d2ac23ce9e14144426235
https://github.com/qemu/qemu/commit/5e003f17ec518cd96f5d2ac23ce9e14144426235
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block.c
M block/block-backend.c
M block/snapshot.c
M include/block/block.h
M migration/block.c
Log Message:
-----------
block: Make bdrv_next() keep strong references
On one hand, it is a good idea for bdrv_next() to return a strong
reference because ideally nearly every pointer should be refcounted.
This fixes intermittent failure of iotest 194.
On the other, it is absolutely necessary for bdrv_next() itself to keep
a strong reference to both the BB (in its first phase) and the BDS (at
least in the second phase) because when called the next time, it will
dereference those objects to get a link to the next one. Therefore, it
needs these objects to stay around until then. Just storing the pointer
to the next in the iterator is not really viable because that pointer
might become invalid as well.
Both arguments taken together means we should probably just invoke
bdrv_ref() and blk_ref() in bdrv_next(). This means we have to assert
that bdrv_next() is always called from the main loop, but that was
probably necessary already before this patch and judging from the
callers, it also looks to actually be the case.
Keeping these strong references means however that callers need to give
them up if they decide to abort the iteration early. They can do so
through the new bdrv_next_cleanup() function.
Suggested-by: Kevin Wolf <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Stefan Hajnoczi <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: c0012e9a22ef23507025daaad01de03dcc928eec
https://github.com/qemu/qemu/commit/c0012e9a22ef23507025daaad01de03dcc928eec
Author: Max Reitz <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M tests/qemu-iotests/087
Log Message:
-----------
iotests: Make 087 pass without AIO enabled
If AIO has not been enabled in the qemu build that is to be tested, we
should skip the "aio=native without O_DIRECT" test instead of failing.
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Max Reitz <address@hidden>
Commit: d5a49c6e7d9e42059450674ec845b7bc0d62cb7e
https://github.com/qemu/qemu/commit/d5a49c6e7d9e42059450674ec845b7bc0d62cb7e
Author: Kevin Wolf <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block.c
M block/block-backend.c
M block/io.c
M block/qapi.c
M block/qcow2-cache.c
M block/qcow2-cluster.c
M block/qcow2-refcount.c
M block/qcow2.c
M block/qcow2.h
M block/replication.c
M block/snapshot.c
M block/vvfat.c
M include/block/block.h
M include/qapi/qmp/qbool.h
M include/qapi/qmp/qdict.h
M include/qapi/qmp/qlist.h
A include/qapi/qmp/qnull.h
M include/qapi/qmp/qnum.h
M include/qapi/qmp/qobject.h
M include/qapi/qmp/qstring.h
M include/qapi/qmp/types.h
M migration/block.c
M qapi/qapi-clone-visitor.c
M qapi/string-input-visitor.c
M qobject/qbool.c
M qobject/qdict.c
M qobject/qlist.c
M qobject/qnull.c
M qobject/qnum.c
M qobject/qobject.c
M qobject/qstring.c
M scripts/coccinelle/qobject.cocci
M tests/.gitignore
M tests/Makefile.include
M tests/check-qnull.c
A tests/check-qobject.c
M tests/qemu-iotests/020
M tests/qemu-iotests/020.out
M tests/qemu-iotests/060
M tests/qemu-iotests/060.out
M tests/qemu-iotests/087
M tests/qemu-iotests/133
M tests/qemu-iotests/133.out
Log Message:
-----------
Merge remote-tracking branch 'mreitz/tags/pull-block-2017-11-17' into
queue-block
Block patches for 2.11.0-rc2
# gpg: Signature made Fri Nov 17 18:22:07 2017 CET
# gpg: using RSA key F407DB0061D5CF40
# gpg: Good signature from "Max Reitz <address@hidden>"
# Primary key fingerprint: 91BE B60A 30DB 3E88 57D1 1829 F407 DB00 61D5 CF40
* mreitz/tags/pull-block-2017-11-17:
iotests: Make 087 pass without AIO enabled
block: Make bdrv_next() keep strong references
qcow2: Fix overly broad madvise()
qcow2: Refuse to get unaligned offsets from cache
qcow2: Add bounds check to get_refblock_offset()
block: Guard against NULL bs->drv
qcow2: Unaligned zero cluster in handle_alloc()
qcow2: check_errors are fatal
qcow2: reject unaligned offsets in write compressed
iotests: Add test for failing qemu-img commit
tests: Add check-qobject for equality tests
iotests: Add test for non-string option reopening
block: qobject_is_equal() in bdrv_reopen_prepare()
qapi: Add qobject_is_equal()
qapi/qlist: Add qlist_append_null() macro
qapi/qnull: Add own header
Signed-off-by: Kevin Wolf <address@hidden>
Commit: 2e02083438962d26ef9dcc7100f3b378104183db
https://github.com/qemu/qemu/commit/2e02083438962d26ef9dcc7100f3b378104183db
Author: Peter Maydell <address@hidden>
Date: 2017-11-17 (Fri, 17 Nov 2017)
Changed paths:
M block.c
M block/block-backend.c
M block/bochs.c
M block/cloop.c
M block/dmg.c
M block/io.c
M block/qapi.c
M block/qcow2-cache.c
M block/qcow2-cluster.c
M block/qcow2-refcount.c
M block/qcow2.c
M block/qcow2.h
M block/rbd.c
M block/replication.c
M block/snapshot.c
M block/vvfat.c
M include/block/block.h
M include/qapi/qmp/qbool.h
M include/qapi/qmp/qdict.h
M include/qapi/qmp/qlist.h
A include/qapi/qmp/qnull.h
M include/qapi/qmp/qnum.h
M include/qapi/qmp/qobject.h
M include/qapi/qmp/qstring.h
M include/qapi/qmp/types.h
M migration/block.c
M qapi/block-core.json
M qapi/qapi-clone-visitor.c
M qapi/string-input-visitor.c
M qobject/qbool.c
M qobject/qdict.c
M qobject/qlist.c
M qobject/qnull.c
M qobject/qnum.c
M qobject/qobject.c
M qobject/qstring.c
M scripts/coccinelle/qobject.cocci
M tests/.gitignore
M tests/Makefile.include
M tests/check-qnull.c
A tests/check-qobject.c
M tests/qemu-iotests/020
M tests/qemu-iotests/020.out
M tests/qemu-iotests/060
M tests/qemu-iotests/060.out
M tests/qemu-iotests/087
M tests/qemu-iotests/133
M tests/qemu-iotests/133.out
M tests/qemu-iotests/176
M tests/qemu-iotests/176.out
M tests/qemu-iotests/182
A tests/qemu-iotests/196
A tests/qemu-iotests/196.out
A tests/qemu-iotests/198
A tests/qemu-iotests/198.out
M tests/qemu-iotests/common.filter
M tests/qemu-iotests/group
Log Message:
-----------
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging
Block layer patches for 2.11.0-rc2
# gpg: Signature made Fri 17 Nov 2017 17:58:36 GMT
# gpg: using RSA key 0x7F09B272C88F2FD6
# gpg: Good signature from "Kevin Wolf <address@hidden>"
# Primary key fingerprint: DC3D EB15 9A9A F95D 3D74 56FE 7F09 B272 C88F 2FD6
* remotes/kevin/tags/for-upstream: (25 commits)
iotests: Make 087 pass without AIO enabled
block: Make bdrv_next() keep strong references
qcow2: Fix overly broad madvise()
qcow2: Refuse to get unaligned offsets from cache
qcow2: Add bounds check to get_refblock_offset()
block: Guard against NULL bs->drv
qcow2: Unaligned zero cluster in handle_alloc()
qcow2: check_errors are fatal
qcow2: reject unaligned offsets in write compressed
iotests: Add test for failing qemu-img commit
tests: Add check-qobject for equality tests
iotests: Add test for non-string option reopening
block: qobject_is_equal() in bdrv_reopen_prepare()
qapi: Add qobject_is_equal()
qapi/qlist: Add qlist_append_null() macro
qapi/qnull: Add own header
qcow2: fix image corruption on commit with persistent bitmap
iotests: test clearing unknown autoclear_features by qcow2
block: Fix permissions in image activation
qcow2: fix image corruption after committing qcow2 image into base
...
Signed-off-by: Peter Maydell <address@hidden>
Compare: https://github.com/qemu/qemu/compare/085ee6d282d3...2e0208343896
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-commits] [qemu/qemu] 611e06: replication: Fix replication open fail,
GitHub <=