From: Laurent Vivier <Laurent@vivier.eu>
To: qemu-devel@nongnu.org
Subject: [Bug 1860920] Re: qemu-s390x-softmmu: crash
Date: Thu, 30 Apr 2020 13:42:25 -0000 [thread overview]
Message-ID: <158825414580.5544.1813182086107458475.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 158005183659.18916.14986952783973408797.malonedeb@gac.canonical.com
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1860920
Title:
qemu-s390x-softmmu: crash
Status in QEMU:
Fix Released
Bug description:
Trying to compile and use rust programs on an s390x emulated machine,
crash in qemu/target/s390x/translate.c line 3894
Steps to reproduce:
on a amd64 PC, installed debian on s390x emulated by qemu, seems to work fine (installed some packages, etc.)
installed rust cargo (either from rustup or from debian)
cargo install anything makes *qemu* crash when beginning to compile
Technical details:
* host: amd64 Linux
* qemu v4.2.0 (recompiled from git with debug options using configure --target-list=s390x-softmmu --enable-debug) (problem appears also with older versions of qemu from git, with default compilation options, with qemu from debian, etc.)
* compiled with gcc 9.2
* command line, relevant part: qemu-system-s390x -snapshot -machine s390-ccw-virtio -cpu max,zpci=on -serial mon:stdio -display none -m 512
(tested with -smp 4 -m 4096 as well and without snapshotting)
* command line, less relevant part: -drive file=./debian.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-ccw,devno=fe.0.0001,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,scsi=off -netdev user,id=mynet0,hostfwd=tcp::2223-:22 -device virtio-net-pci,netdev=mynet0
* core dump: abort in qemu/target/s390x/translate.c line 3894 ; s->field: op has value 0xEC and op2 has value 0x54
(more info available if needed)
Tried to patch source to add 0x54 case to no avail.
Tried other cpu variants to no avail as well.
Reporting this in security as well since it also looks very much like
a DoS (albeit somewhat minor), feel free to tell me to report the bug
somewhere else.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1860920/+subscriptions
prev parent reply other threads:[~2020-04-30 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <158005183659.18916.14986952783973408797.malonedeb@gac.canonical.com>
2020-01-30 8:18 ` [Bug 1860920] Re: qemu-s390x-softmmu: crash Thomas Huth
2020-01-30 8:30 ` Thomas Huth
2020-01-31 9:40 ` Thomas Huth
2020-01-31 10:00 ` Jean-Gabriel Kammerer
2020-03-10 9:13 ` Laurent Vivier
2020-04-30 13:42 ` Laurent Vivier [this message]
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=158825414580.5544.1813182086107458475.launchpad@soybean.canonical.com \
--to=laurent@vivier.eu \
--cc=1860920@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.