On Sat, Aug 16, 2003 at 11:16:57AM +0300, Ognyan Kulev wrote: > proc also uses the task port given by rpctrace. So one can write a > program that passes fake task port to proc, and when proc tries to > handle the fake process in some way, the whole proc server will hang > because it is single-threaded. Isn't it principally like the > thread_resume case?
What task port? The only problem I can see is that proc_child will happily add the user supplied task port to the task list, which seems wrong. In fact, I wonder if fork works at all in rpctrace, but probably it does. It makes me wonder why and if there are any ill effects, though. That it simply adds the task port in proc_child might in fact mean that it uses the user supplied task port as you indicate, but I am not sure you meant that. Thanks, Marcus -- `Rhubarb is no Egyptian god.' GNU http://www.gnu.org [EMAIL PROTECTED] Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/ [EMAIL PROTECTED] http://www.marcus-brinkmann.de/ _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
