public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@admin.navo.hpc.mil>
To: Axel Kittenberger <Axel.Kittenberger@maxxio.com>,
	linux-kernel@vger.kernel.org
Cc: riel@nl.linux.org
Subject: Re: Patch: oom_kill
Date: Tue, 4 Feb 2003 08:55:14 -0600	[thread overview]
Message-ID: <200302040855.14469.pollard@admin.navo.hpc.mil> (raw)
In-Reply-To: <200302041513.29093.Axel.Kittenberger@maxxio.com>

On Tuesday 04 February 2003 08:13 am, Axel Kittenberger wrote:
> > And what about processes that get reparented to init? These could be
> > causing the OOM. I didn't think that the p_ptr was null when reparenting
> > happens.
>
> Okay good, should we use the "original parent" instead?

I'm not familiar enough with the reparenting to know. I'm not sure you can 
tell the difference.

> Yes, I'm not absolutly not sure if the != NULL expression is necessary,
> Don't know enough about the task structering for this. I tried without and
> the machine at least didn't crash, but just wanted to be safe.

I was considering that a possible test for a reparented process since the
original parent doesn't necessarily exist anymore, though it would make
more sense to have that point to init, than point to anything else.

-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

      reply	other threads:[~2003-02-04 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 12:32 Patch: oom_kill Axel Kittenberger
2003-02-04 14:07 ` Jesse Pollard
2003-02-04 14:13   ` Axel Kittenberger
2003-02-04 14:55     ` Jesse Pollard [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=200302040855.14469.pollard@admin.navo.hpc.mil \
    --to=pollard@admin.navo.hpc.mil \
    --cc=Axel.Kittenberger@maxxio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@nl.linux.org \
    /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