From: Mike Galbraith <efault@gmx.de>
To: Albert Cahalan <acahalan@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG: wedged processes, test program supplied
Date: Wed, 20 Dec 2006 08:09:25 +0100 [thread overview]
Message-ID: <1166598565.1614.53.camel@Homer.simpson.net> (raw)
In-Reply-To: <787b0d920612192205v2d650361r4f737c41aa1d3a92@mail.gmail.com>
On Wed, 2006-12-20 at 01:05 -0500, Albert Cahalan wrote:
> On 12/20/06, Mike Galbraith <efault@gmx.de> wrote:
> > On Tue, 2006-12-19 at 21:46 -0500, Albert Cahalan wrote:
> > > Somebody PLEASE try this...
> >
> > I was having enough fun with cloninator (which was whitespace munged
> > btw).
>
> Anything stuck? Besides refusing to die, that beast slays debuggers
> left and right. I just need to add execve of /proc/self/exe and a massive
> storm of signals on the alternate stack.
Usually, I can kill the misbehaving strace or abandoned cloninators if
it decides to take a hike, but sometimes it leaves corpses lying around.
> Oh. I wanted to be sure you'd see the problem. Did you have
> some... difficulty? A plain old ^C should make things stop.
> The second test program is like the first, but missing SIGCHLD
> >from the clone flags, and hopefully not whitespace-mangled.
>
> Note that the test program is not normally a fork bomb.
> It self-limits itself to 42 tasks via a lock in shared memory.
> If things are working OK, you should see no more than
> about 60 tasks.
I didn't take any countermeasures.. had ~27000 zombies.
-Mike
prev parent reply other threads:[~2006-12-20 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 2:46 Albert Cahalan
2006-12-20 5:40 ` Mike Galbraith
2006-12-20 6:05 ` Albert Cahalan
2006-12-20 7:09 ` Mike Galbraith [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=1166598565.1614.53.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=acahalan@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®