linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Gerd Knorr <kraxel@bytesex.org>,
	User-mode Linux Kernel Development
	<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Re: pthreads?
Date: Sat, 13 Sep 2003 14:53:32 -0400	[thread overview]
Message-ID: <200309131853.h8DIrWe4006808@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Sat, 13 Sep 2003 00:25:00 +0200." <Pine.LNX.4.44.0309130019420.19429-100000@filer.marasystems.com>

hno@marasystems.com said:
> If you think it is feasible to run another heavy user of clone(),
> message queues and signals in the same process then it might be.. but
> my gut feeling is not.. 

The only thing that worries me about clone is wait().  wait(-1, ...) is 
obviously dangerous if there are children floating around that you don't
know about.  Any properly careful user of wait will call it with the pids
of children that it knows about.  UML is not properly careful...

Signals can be handled cleanly if handlers are chained.

I don't know what message queues are.  UML doesn't use anything by that name.

However, I didn't think of the possibility of pthreads overriding system calls.
That opens up whole new vistas of brokenness.

				Jeff



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2003-09-13 18:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 15:54 [uml-devel] pthreads? Geert Uytterhoeven
2003-09-11 17:55 ` Jeff Dike
2003-09-12  8:52 ` [uml-devel] pthreads? Gerd Knorr
2003-09-12  9:07   ` Geert Uytterhoeven
2003-09-12 11:08     ` Gerd Knorr
2003-09-12 11:18       ` Geert Uytterhoeven
2003-09-12 12:15         ` Gerd Knorr
2003-09-12 12:17           ` Geert Uytterhoeven
2003-09-12 11:18     ` Henrik Nordstrom
2003-09-12 16:28       ` Jeff Dike
2003-09-12 22:25         ` Henrik Nordstrom
2003-09-13 18:53           ` Jeff Dike [this message]
2003-09-13 21:01             ` Henrik Nordstrom
2003-09-13 15:24         ` Geert Uytterhoeven
2003-09-13 18:54           ` Jeff Dike
2003-09-15  6:57             ` Geert Uytterhoeven
2003-09-15  9:19               ` Henrik Nordstrom
2003-09-15  9:28                 ` Geert Uytterhoeven
2003-09-15 10:51                   ` Henrik Nordstrom
2003-09-16 18:44                     ` BlaisorBlade
2003-10-02  9:20                 ` Jan Hudec
2003-10-02  9:08     ` Jan Hudec
2003-10-02  9:24       ` Geert Uytterhoeven
2003-10-02  9:31         ` Jan Hudec
     [not found]           ` <Pine.GSO.4.21.0310021146500.8567-100000@vervain.sonytel.be>
2003-10-02 13:52             ` Jan Hudec
2003-10-02 14:28               ` Geert Uytterhoeven
2003-10-02 14:42                 ` Jan Hudec
2003-10-07 15:51                   ` The Story Continues (was: Re: [uml-devel] Re: pthreads?) Geert Uytterhoeven
2003-10-11  1:48                     ` Jeff Dike
2003-10-11  8:39                       ` Geert Uytterhoeven
2003-10-12  9:53                     ` Geert Uytterhoeven
2003-10-06 13:29       ` [uml-devel] Re: pthreads? BlaisorBlade
  -- strict thread matches above, loose matches on Subject: below --
2003-09-12 12:30 stian

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=200309131853.h8DIrWe4006808@ccure.karaya.com \
    --to=jdike@addtoit.com \
    --cc=geert@linux-m68k.org \
    --cc=hno@marasystems.com \
    --cc=kraxel@bytesex.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox