[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PATCH: proc_do_stop and rpctrace

From: Marcus Brinkmann
Subject: Re: PATCH: proc_do_stop and rpctrace
Date: Sat, 16 Aug 2003 14:29:41 +0200
User-agent: Mutt/1.5.4i

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.


`Rhubarb is no Egyptian god.' GNU      http://www.gnu.org    marcus@gnu.org
Marcus Brinkmann              The Hurd http://www.gnu.org/software/hurd/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]