All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-user mmap not thread-safe?
Date: Thu, 24 May 2007 17:00:16 +0200	[thread overview]
Message-ID: <4655A880.2000801@suse.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

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?

If anyone more experienced in the mmap internals of qemu could take a
look at this I'd be really glad Appended is the source file as well as
the compiled i386 binary (glibc 2.3 w/o TLS) to trigger this.

The very same executable works just fine on a real pc.

Thanks a lot,

Alexander Graf

[-- Attachment #2: clone.tgz --]
[-- Type: application/x-compressed-tar, Size: 4392 bytes --]

             reply	other threads:[~2007-05-24 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 15:00 Alexander Graf [this message]
2007-05-24 15:45 ` [Qemu-devel] qemu-user mmap not thread-safe? Paul Brook
2007-06-19 14:04   ` Alexander Graf
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=4655A880.2000801@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 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.