lkml.org 
[lkml]   [1999]   [Jan]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Porting vfork()
Date
> 
>
>
> On Fri, 8 Jan 1999, Perry Harrington wrote:
> > >
> > > Hmm... I do wonder about what happens to signals while vfork() is blocking
> > > the parent, though. Ick. The parent invoking signal handlers isn't much
> > > better then the child invoking signal handlers. One longjmp(), and
> > > everything gets confused. Temporarily block all signals to the parent but
> > > SIGKILL? Perhaps the only solution. And how does the child cleanly release
> > > the wait_queue in its parent if its parent may have been killed in the
> > > meantime?
> >
> > That's a good question, do you want to temporarily block signals to the parent?
>
> No need to. If you use sleep_on(), the parent won't be getting any signals
> anyway (only sleep_on_interruptible() cares about signals).

That's what I thought I recalled from the Rubini book.

>
> Linus
>


--
Perry Harrington Linux rules all OSes. APSoft ()
email: perry@apsoft.com Think Blue. /\

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:49    [W:0.090 / U:0.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site