public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
	Florian Mickler <florian@mickler.org>,
	Ingo Molnar <mingo@elte.hu>, Dave Chinner <david@fromorbit.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [regression, 2.6.37-rc1] 'ip link tap0 up' stuck in do_exit()
Date: Thu, 09 Dec 2010 18:07:54 +0100	[thread overview]
Message-ID: <1291914474.4063.68.camel@edumazet-laptop> (raw)
In-Reply-To: <20101209164748.GA3218@hack>

Le vendredi 10 décembre 2010 à 00:47 +0800, Américo Wang a écrit :

> Yeah, there is no point that a zombie can trigger a BUG_ON in kenrel.
> But it is still interesting to know why it becomes a zombie...
> 

A zombie is very easy to get.

Technically speaking, all processes die and become zombies, unless
parent said : signal(SIGCLD, SIG_IGN) before fork()

The parent is buggy (sudo in this case ?) and doesnt call wait() to
'free' one of its children.

  reply	other threads:[~2010-12-09 17:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03  6:26 [regression, 2.6.37-rc1] 'ip link tap0 up' stuck in do_exit() Dave Chinner
2010-11-03  7:13 ` Eric Dumazet
2010-11-03 10:34   ` Dave Chinner
2010-11-03 11:29     ` Dave Chinner
2010-11-04  0:21       ` Dave Chinner
2010-11-04  5:47         ` Américo Wang
2010-12-08  9:02           ` Florian Mickler
2010-12-08 13:41             ` Oleg Nesterov
2010-12-08 13:47               ` Oleg Nesterov
2010-12-08 14:08                 ` Oleg Nesterov
2010-12-09 16:47                   ` Américo Wang
2010-12-09 17:07                     ` Eric Dumazet [this message]
2010-12-09 17:09                       ` Eric Dumazet
2010-12-09 17:59                     ` Jim Bos

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=1291914474.4063.68.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=david@fromorbit.com \
    --cc=florian@mickler.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=xiyou.wangcong@gmail.com \
    /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