From: Eric Blake <eblake@redhat.com>
To: linzhecheng <linzhecheng@huawei.com>, qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, famz@redhat.com, wangxinxin.wang@huawei.com,
arei.gonglei@huawei.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4] thread: move detach_thread from creating thread to created thread
Date: Wed, 29 Nov 2017 10:18:51 -0600 [thread overview]
Message-ID: <cd2bad80-1790-aa01-fde4-4979b4c53b97@redhat.com> (raw)
In-Reply-To: <20171128044656.10592-1-linzhecheng@huawei.com>
On 11/27/2017 10:46 PM, linzhecheng wrote:
> If we create a thread with QEMU_THREAD_DETACHED mode, QEMU may get a segfault in a low probability.
>
>
> The root cause of this problem is a bug of glibc(version 2.17,the latest version has the same bug),
> let's see what happened in glibc's code.
Have you reported this bug to the glibc folks, and if so, can we include
a URL to the glibc bugzilla?
Working around the glibc bug is nice, but glibc should really be fixed
so that other projects do not have to continue working around it.
>
> QEMU get a segfault at line 50, becasue pd is an invalid address.
> pd is still valid at line 38 when set pd->joinid = pd, at this moment,
> created thread is just exiting(only keeps runing for a short time),
s/runing/running/
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2017-11-29 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 4:46 [Qemu-devel] [PATCH v4] thread: move detach_thread from creating thread to created thread linzhecheng
2017-11-28 6:27 ` Fam Zheng
2017-11-29 16:18 ` Eric Blake [this message]
2017-11-29 16:28 ` Gonglei (Arei)
2017-11-29 16:38 ` Paolo Bonzini
2017-11-29 16:41 ` Gonglei (Arei)
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=cd2bad80-1790-aa01-fde4-4979b4c53b97@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=arei.gonglei@huawei.com \
--cc=famz@redhat.com \
--cc=linzhecheng@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
/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).