~ubuntu-virt/qemu/+git/qemu-lp-import:stable-4.2

Last commit made on 2020-06-25
Get this branch:
git clone -b stable-4.2 https://git.launchpad.net/~ubuntu-virt/qemu/+git/qemu-lp-import

Branch merges

Branch information

Name:
stable-4.2
Repository:
lp:~ubuntu-virt/qemu/+git/qemu-lp-import

Recent commits

6cdf8c4... by Michael Roth

Update version for 4.2.1 release

4a0db6b... by Kevin Wolf

iotests/283: Use consistent size for source and target

The test case forgot to specify the null-co size for the target node.
When adding a check to backup that both sizes match, this would fail
because of the size mismatch and not the behaviour that the test really
wanted to test.

Fixes: a541fcc27c98b96da187c7d4573f3270f3ddd283
Signed-off-by: Kevin Wolf <email address hidden>
Message-Id: <email address hidden>
Reviewed-by: Vladimir Sementsov-Ogievskiy <email address hidden>
Signed-off-by: Kevin Wolf <email address hidden>
(cherry picked from commit 813cc2545b82409fd504509f0ba2e96fab6edb9e)
Signed-off-by: Michael Roth <email address hidden>

0664ffa... by Helge Deller

Fix tulip breakage

The tulip network driver in a qemu-system-hppa emulation is broken in
the sense that bigger network packages aren't received any longer and
thus even running e.g. "apt update" inside the VM fails.

The breakage was introduced by commit 8ffb7265af ("check frame size and
r/w data length") which added checks to prevent accesses outside of the
rx/tx buffers.

But the new checks were implemented wrong. The variable rx_frame_len
counts backwards, from rx_frame_size down to zero, and the variable len
is never bigger than rx_frame_len, so accesses just can't happen and the
checks are unnecessary.
On the contrary the checks now prevented bigger packages to be moved
into the rx buffers.

This patch reverts the wrong checks and were sucessfully tested with a
qemu-system-hppa emulation.

Fixes: 8ffb7265af ("check frame size and r/w data length")
Buglink: https://bugs.launchpad.net/bugs/1874539
Signed-off-by: Helge Deller <email address hidden>
Signed-off-by: Jason Wang <email address hidden>
(cherry picked from commit d9b69640391618045949f7c500b87fc129f862ed)
Signed-off-by: Michael Roth <email address hidden>

27f56b9... by lixinyu <email address hidden>

tcg/mips: mips sync* encode error

OPC_SYNC_WMB, OPC_SYNC_MB, OPC_SYNC_ACQUIRE, OPC_SYNC_RELEASE and
OPC_SYNC_RMB have wrong encode. According to the mips manual,
their encode should be 'OPC_SYNC | 0x?? << 6' rather than
'OPC_SYNC | 0x?? << 5'. Wrong encode can lead illegal instruction
errors. These instructions often appear with multi-threaded
simulation.

Fixes: 6f0b99104a3 ("tcg/mips: Add support for fence")
Reviewed-by: Richard Henderson <email address hidden>
Reviewed-by: Aleksandar Markovic <email address hidden>
Reviewed-by: Philippe Mathieu-Daudé <email address hidden>
Signed-off-by: lixinyu <email address hidden>
Message-Id: <email address hidden>
Signed-off-by: Richard Henderson <email address hidden>
(cherry picked from commit a4e57084c16d5b0eff3651693fba04f26b30b551)
Signed-off-by: Michael Roth <email address hidden>

97701bc... by jcmvbkbc

target/xtensa: fix pasto in pfwait.r opcode name

Core xtensa opcode table has pfwait.o instead of pfwait.r. Fix that.

Fixes: c884400f2988 ("target/xtensa: implement block prefetch option opcodes")
Signed-off-by: Max Filippov <email address hidden>
(cherry picked from commit 1a03362b14affa4d8ddede55df6e21d7a07b87c2)
Signed-off-by: Michael Roth <email address hidden>

ecdb0d5... by Kevin Wolf

vpc: Don't round up already aligned BAT sizes

As reported on Launchpad, Azure apparently doesn't accept images for
upload that are not both aligned to 1 MB blocks and have a BAT size that
matches the image size exactly.

As far as I can tell, there is no real reason why we create a BAT that
is one entry longer than necessary for aligned image sizes, so change
that.

(Even though the condition is only mentioned as "should" in the spec and
previous products accepted larger BATs - but we'll try to maintain
compatibility with as many of Microsoft's ever-changing interpretations
of the VHD spec as possible.)

Fixes: https://bugs.launchpad.net/bugs/1870098
Reported-by: Tobias Witek
Signed-off-by: Kevin Wolf <email address hidden>
Message-Id: <email address hidden>
Reviewed-by: Max Reitz <email address hidden>
Reviewed-by: Philippe Mathieu-Daudé <email address hidden>
Signed-off-by: Kevin Wolf <email address hidden>
(cherry picked from commit 3f6de653b946fe849330208becf79d6af7e876cb)
Signed-off-by: Michael Roth <email address hidden>

9c2e242... by David Gibson <email address hidden>

spapr: Fix failure path for attempting to hot unplug PCI bridges

For various technical reasons we can't currently allow unplug a PCI to PCI
bridge on the pseries machine. spapr_pci_unplug_request() correctly
generates an error message if that's attempted.

But.. if the given errp is not error_abort or error_fatal, it doesn't
actually stop trying to unplug the bridge anyway.

Fixes: 14e714900f6b "spapr: Allow hot plug/unplug of PCI bridges and devices under PCI bridges"
Signed-off-by: David Gibson <email address hidden>
Reviewed-by: Greg Kurz <email address hidden>
(cherry picked from commit 7aab5899764887f6b0512cb2e5c11bdc2a5d3644)
Signed-off-by: Michael Roth <email address hidden>

fb6a24f... by P J P

net: tulip: check frame size and r/w data length

Tulip network driver while copying tx/rx buffers does not check
frame size against r/w data length. This may lead to OOB buffer
access. Add check to avoid it.

Limit iterations over descriptors to avoid potential infinite
loop issue in tulip_xmit_list_update.

Reported-by: Li Qiang <email address hidden>
Reported-by: Ziming Zhang <email address hidden>
Reported-by: Jason Wang <email address hidden>
Tested-by: Li Qiang <email address hidden>
Reviewed-by: Li Qiang <email address hidden>
Signed-off-by: Prasad J Pandit <email address hidden>
Signed-off-by: Jason Wang <email address hidden>
(cherry picked from commit 8ffb7265af64ec81748335ec8f20e7ab542c3850)
Signed-off-by: Michael Roth <email address hidden>

60c21aa... by Eric Blake

sheepdog: Consistently set bdrv_has_zero_init_truncate

block_int.h claims that .bdrv_has_zero_init must return 0 if
.bdrv_has_zero_init_truncate does likewise; but this is violated if
only the former callback is provided if .bdrv_co_truncate also exists.
When adding the latter callback, it was mistakenly added to only one
of the three possible sheepdog instantiations.

Fixes: 1dcaf527
Signed-off-by: Eric Blake <email address hidden>
Message-Id: <email address hidden>
Reviewed-by: John Snow <email address hidden>
Reviewed-by: Philippe Mathieu-Daudé <email address hidden>
Signed-off-by: Max Reitz <email address hidden>
(cherry picked from commit ed049910637be991c88cc25c864115bc5b1e4dab)
Signed-off-by: Michael Roth <email address hidden>

5eca12b... by Eric Blake

qcow2: List autoclear bit names in header

The feature table is supposed to advertise the name of all feature
bits that we support; however, we forgot to update the table for
autoclear bits. While at it, move the table to read-only memory in
code, and tweak the qcow2 spec to name the second autoclear bit.
Update iotests that are affected by the longer header length.

Fixes: 88ddffae
Fixes: 93c24936
Signed-off-by: Eric Blake <email address hidden>
Reviewed-by: Vladimir Sementsov-Ogievskiy <email address hidden>
Message-Id: <email address hidden>
Signed-off-by: Max Reitz <email address hidden>
(cherry picked from commit bb40ebce2cb0bd4bf37968074d43d5a864fb6dee)
Signed-off-by: Michael Roth <email address hidden>