From: "Sven Köhler" <skoehler@upb.de>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Rob Landley <rob@landley.net>, Antoine Martin <antoine@nagafix.co.uk>
Subject: [uml-devel] Re: tls: set_thread_area failed
Date: Wed, 14 Dec 2005 04:05:46 +0100 [thread overview]
Message-ID: <439F8C0A.2000302@upb.de> (raw)
In-Reply-To: <87fyowsjkg.fsf@amaterasu.srvr.nix>
> e2fsprogs-1.38/misc/fsck.c:check_all() repeatedly invokes fsck_device(),
> which invokes execute(), which does a perfectly normal fork()/exec().
> No threads here. Nor is there use of aio_*(), which might use threads
> (well, POSIX allows it).
Sorry, and what's the conclusion?
fork() calles set_thread_area()?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-12-14 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 2:13 [uml-devel] tls: set_thread_area failed Antoine Martin
2005-12-09 17:52 ` Blaisorblade
2005-12-09 18:39 ` Antoine Martin
2005-12-10 14:26 ` Blaisorblade
2005-12-10 16:31 ` Antoine Martin
2005-12-11 6:34 ` Rob Landley
2005-12-11 16:01 ` Blaisorblade
2005-12-13 22:45 ` Nix
2005-12-14 3:05 ` Sven Köhler [this message]
2005-12-14 12:21 ` [uml-devel] " Blaisorblade
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=439F8C0A.2000302@upb.de \
--to=skoehler@upb.de \
--cc=antoine@nagafix.co.uk \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.