From: Peter Maydell <1808565@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1808565] Re: Reading /proc/self/task/<pid>/maps is not remapped to the target
Date: Tue, 20 Apr 2021 09:22:57 -0000 [thread overview]
Message-ID: <161891057765.5292.242097580400785304.malone@soybean.canonical.com> (raw)
In-Reply-To: 154480990326.22999.12064081216456974155.malonedeb@soybean.canonical.com
Code inspection shows we still don't handle /proc/self/task.
** Changed in: qemu
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1808565
Title:
Reading /proc/self/task/<pid>/maps is not remapped to the target
Status in QEMU:
Confirmed
Bug description:
Seeing this in qemu-user 3.1.0
The code in is_proc_myself which supports remapping of /proc/self/maps
and /proc/<pid>/maps does not support remapping of
/proc/self/task/<pid>/maps or /proc/<pid>/task/<pid>/maps. Extending
is_proc_myself to cover these cases causes the maps to be rewritten
correctly.
These are useful in multithreaded programs to avoid freezing the
entire program to capture the maps for a single tid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1808565/+subscriptions
next prev parent reply other threads:[~2021-04-20 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 17:51 [Qemu-devel] [Bug 1808565] [NEW] Reading /proc/self/task/<pid>/maps is not remapped to the target Alan Jones
2021-04-20 6:51 ` [Bug 1808565] " Thomas Huth
2021-04-20 9:22 ` Peter Maydell [this message]
2021-05-09 15:10 ` Thomas Huth
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=161891057765.5292.242097580400785304.malone@soybean.canonical.com \
--to=1808565@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.