From: Launchpad Bug Tracker <1918149@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1918149] Re: qemu-user reports wrong fault_addr in signal handler
Date: Wed, 14 Jul 2021 04:17:21 -0000 [thread overview]
Message-ID: <162623624174.32682.11832246798693352029.malone@loganberry.canonical.com> (raw)
In-Reply-To: 161521552307.29654.2972591810140156041.malonedeb@wampee.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1918149
Title:
qemu-user reports wrong fault_addr in signal handler
Status in QEMU:
Expired
Bug description:
When a SEGV signal occurs and si_addr of the info struct is nil, qemu
still tries to translate the address from host to guest
(handle_cpu_signal in accel/tcg/user-exec.c). This means, that the
actual signal handler, will receive a fault_addr that is something
like 0xffffffffbf709000.
I was able to get this to happen, by branching to a non canonical address on aarch64.
I used 5.2 (commit: 553032db17). However, building from source, this only seems to happen, if I use the same configure flags as the debian build:
../configure --static --target-list=aarch64-linux-user --disable-
system --enable-trace-backends=simple --disable-linux-io-uring
--disable-pie --extra-cflags="-fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --extra-
ldflags="-Wl,-z,relro -Wl,--as-needed"
Let me know, if you need more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1918149/+subscriptions
prev parent reply other threads:[~2021-07-14 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 14:58 [Bug 1918149] [NEW] qemu-user reports wrong fault_addr in signal handler Leonardo
2021-03-11 18:45 ` [Bug 1918149] " Peter Maydell
2021-05-14 18:49 ` Thomas Huth
2021-07-14 4:17 ` Launchpad Bug Tracker [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=162623624174.32682.11832246798693352029.malone@loganberry.canonical.com \
--to=1918149@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.