From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-user mmap not thread-safe?
Date: Tue, 19 Jun 2007 16:04:16 +0200 [thread overview]
Message-ID: <4677E260.2080002@suse.de> (raw)
In-Reply-To: <200705241645.58693.paul@codesourcery.com>
Paul Brook wrote:
> On Thursday 24 May 2007, Alexander Graf wrote:
>
>> Hi,
>>
>> while playing around with TLS on i386 i came across this problem which
>> occurs even when no TLS is used at all. If two threads just malloc()
>> memory all the time I get a segmentation fault after a short time. Might
>> this be a serious bug?
>>
>
> qemu is not even vaguely threadsafe.
>
> Paul
>
>
>
Hi,
I somehow narrowed the problem down to x86_64. As soon as I use
qemu-i386 on i386 or ppc the memory mapping tables are OK. When using
x86_64 as host they are broken. Could this be a generic 64-bit host
problem? I doubt that this actually has to do too much with the
threading itself, because it works fine on other platforms.
Alex
next prev parent reply other threads:[~2007-06-19 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 15:00 [Qemu-devel] qemu-user mmap not thread-safe? Alexander Graf
2007-05-24 15:45 ` Paul Brook
2007-06-19 14:04 ` Alexander Graf [this message]
2007-06-20 9:32 ` Kirill A. Shutemov
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=4677E260.2080002@suse.de \
--to=agraf@suse.de \
--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).