From: Thomas Huth <1066909@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1066909] Re: App-level clone emulation for microblaze is broken
Date: Thu, 19 Jan 2017 14:18:40 -0000 [thread overview]
Message-ID: <20170119141842.25029.18760.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 20121015142611.16277.97828.malonedeb@wampee.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/1066909
Title:
App-level clone emulation for microblaze is broken
Status in QEMU:
Fix Released
Bug description:
When CLONE_THREAD is used, the new process starts with the program
counter pointing to the system call instruction, rather than the
instruction immediately following it. This causes an infinite cascade
(linear growth, not exponential) of thread creation, which quickly
crashes when the threads start running and they're all using the same
stack.
I'm using qemu 1.1.2 packaged with Debian, but I'm not aware of any
fixes since then that would address the problem.
I can provide a test program if needed; a short C program using
syscall() directly or an even-shorter asm program can demonstrate the
issue without need for debugging around pthread library routines.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1066909/+subscriptions
prev parent reply other threads:[~2017-01-19 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 14:26 [Qemu-devel] [Bug 1066909] [NEW] App-level clone emulation for microblaze is broken Bugdal
2012-10-16 1:18 ` [Qemu-devel] [Bug 1066909] " Bugdal
2012-10-20 20:01 ` Bugdal
2012-10-21 0:29 ` Aurelien Jarno
2017-01-19 14:18 ` Thomas Huth [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=20170119141842.25029.18760.launchpad@wampee.canonical.com \
--to=1066909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).