~sergiodj/ubuntu/+source/qemu:wrong-code-execution-s390x-tcg-jammy

Branch merges

Propose for merging

Approved for merging into ubuntu/+source/qemu:ubuntu/jammy-devel

git-ubuntu bot: Approve on 2024-02-21

Athos Ribeiro (community): Approve on 2024-02-21

Canonical Server Core Reviewers: Pending requested 2024-02-21

Canonical Server Reporter: Pending requested 2024-02-21

Diff: 174 lines (+146/-0)

4 files modified

debian/changelog (+8/-0)
debian/patches/series (+2/-0)
debian/patches/ubuntu/lp-2046439-s390x-Fix-emulation-of-C-G-HRL.patch (+53/-0)
debian/patches/ubuntu/lp-2046439-target-s390x-Split-out-gen_ri2.patch (+83/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

189eb9d... by Sergio Durigan Junior on 2024-02-21

changelog for 1:6.2+dfsg-2ubuntu6.18

e9ff317... by Sergio Durigan Junior on 2024-01-03

  * d/p/u/lp-2046439-s390x-*.patch: Fix emulation of
    "COMPARE HALFWORD RELATIVE LONG" on s390x.
    (LP: #2046439)

8375d25... by Christian Ehrhardt  on 2024-01-29

changelog: avoid restarting run-qemu.mount (LP: #2051153)

Signed-off-by: Christian Ehrhardt <email address hidden>

170886a... by Christian Ehrhardt  on 2024-01-29

d/rules: modify qemu-block-extra postinst to avoid restarting run-qemu.mount (LP: #2051153)

A restart of the mount unit can affect qemu running with .so files
loaded from that path and jeopardizes the reason why the mount
unit exists (to allow still running qemu to load .so after upgrades).

Before Jammy it was no mount unit yet and afterwards dh_installsystemd
handles mount units much better. But in Jammy we have the following
situation:

1. calling dh_installsystemd for run-qemu.mount with --no-restart-on-upgrade
  => Ignores --no-restart-on-upgrade and restarts the unit each upgrade
2. Not calling dh_installsystemd for run-qemu.mount
  => picks up the unit with defaults and restarts the unit each upgrade
3. Calling dh_installsystemd for run-qemu.mount but with --no-start --no-enable
  => ignores --no-start and restarts the unit each upgrade
4. Calling dh_installsystemd with --exclude=run-qemu.mount
  => ignores --exclude and restarts the unit each upgrade

Hence we sadly need modify the postinst after the auto-generation
via dh_* tools to skip the line that would restart it.

We already had code that does the enable and start correctly
as that was needed in other versions too - therefore disabling this
is without negative consequences.

Signed-off-by: Christian Ehrhardt <email address hidden>

8fe3adf... by Marc Deslauriers on 2023-11-30

1:6.2+dfsg-2ubuntu6.16 (patches unapplied)

Imported using git-ubuntu import.

81119c5... by Mitchell Dzurick on 2023-09-15

changelog

0cffede... by Mitchell Dzurick on 2023-09-15

* d/rules: remove --no-start for qemu-guest-agent (LP: #2028124)

20e2b1e... by Sergio Durigan Junior on 2023-09-06

changelog for 1:6.2+dfsg-2ubuntu6.14

f29bc87... by Sergio Durigan Junior on 2023-09-06

  * d/u/lp-2033957-virtiofsd-Fix-breakage-due-to-fuse_init_in.patch:
    Fix virtiofsd breakage due to fuse_init_in size change, which
    happened because of the Linux kernel 5.17 headers that were
    imported in a previous patch. (LP: #2033957)

90405aa... by Sergio Durigan Junior on 2023-07-05

changelog for 1:6.2+dfsg-2ubuntu6.13