public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Werner Almesberger <wa@almesberger.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: anyone ever implemented a reparent(pid) syscall?
Date: Mon, 12 May 2003 10:03:04 -0400	[thread overview]
Message-ID: <3EBFA998.7010401@nortelnetworks.com> (raw)
In-Reply-To: 20030512043343.A1861@almesberger.net

Werner Almesberger wrote:

> You'd still have a PID reuse race. Of course, you could also
> cover this by checking the process' start time ...

Good point.  It is unlikely this will happen in our scenario (very long-lived 
processes), but we should certainly cover that case.

> But just designing the parent to be simple enough to be reliable
> and/or generic enough that it doesn't even need to be upgraded
> still looks like a more promising approach to me.

That would be the simple solution.  However, it doesn't cover the case of a 
cosmic ray causing a segfault, or the OOM killer coming along, or root 
accidentally doing a kill -9 on the wrong pid, or other similar issues.

Chris



-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


      reply	other threads:[~2003-05-12 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 18:54 anyone ever implemented a reparent(pid) syscall? Chris Friesen
2003-05-10  9:39 ` Werner Almesberger
2003-05-12  3:23   ` Chris Friesen
2003-05-12  7:33     ` Werner Almesberger
2003-05-12 14:03       ` Chris Friesen [this message]

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=3EBFA998.7010401@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa@almesberger.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