kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: riel@surriel.com (Rik van Riel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Does Linux process exist information leakage?
Date: Thu, 19 Jan 2012 15:23:32 -0500	[thread overview]
Message-ID: <4F187BC4.4040001@surriel.com> (raw)
In-Reply-To: <ff80b878-eadf-4644-a84b-072a1e0563b0@email.android.com>

On 01/11/2012 01:44 PM, Greg Freemyer wrote:

> When a linux process dies, it first becomes a zombie and the parent process is signaled.
>
> The parent process at that point can still do various things.  If the parent is a debugger, it can get all sorts of details from the zombie.
>
> When the parent acknowledges the death of child signal, the zombie is really killed and removed from the system tables, etc.

The memory of a process is freed before it becomes a zombie.

  reply	other threads:[~2012-01-19 20:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 12:53 Does Linux process exist information leakage? 夏业添
2012-01-11 16:23 ` Jonathan Neuschäfer
2012-01-11 16:45 ` Dave Hylands
2012-01-11 17:52   ` Scott Lovenberg
2012-01-12  2:14     ` 夏业添
2012-01-12 17:00     ` Jonathan Neuschäfer
2012-01-16 18:19       ` Scott Lovenberg
2012-01-16 23:45         ` Jonathan Neuschäfer
2012-01-19 14:47           ` Scott Lovenberg
2012-01-16 18:45       ` Greg Freemyer
2012-01-16 20:44         ` Scott Lovenberg
2012-01-12  2:05   ` 夏业添
2012-01-11 18:44 ` Greg Freemyer
2012-01-19 20:23   ` Rik van Riel [this message]
     [not found] ` <CAOfVmNFuBCjWb7-5rJaU7ksgcU8LyAW15JiEwa2PigZL3zC0aw@mail.gmail.com>
2012-01-12  2:30   ` 夏业添
2012-01-18  1:53 ` Fredrick
     [not found]   ` <CAOfVmNFN-GLDwkfLKG11iw7-p6KerDmyoMxV1oSD5WSYJMXc0g@mail.gmail.com>
2012-01-18 11:43     ` beyond.hack
2012-01-19  1:27   ` 夏业添
2012-01-19  7:12     ` SaNtosh kuLkarni
2012-01-19  8:37       ` SaNtosh kuLkarni
2012-01-20  6:52     ` Fredrick
2012-01-19 14:48   ` Scott Lovenberg

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=4F187BC4.4040001@surriel.com \
    --to=riel@surriel.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).