linux-kernel - Re: BUG: wedged processes, test program supplied

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1166598565.1614.53.camel@Homer.simpson.net>
Date:	Wed, 20 Dec 2006 08:09:25 +0100
From:	Mike Galbraith <efault@....de>
To:	Albert Cahalan <acahalan@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: BUG: wedged processes, test program supplied

On Wed, 2006-12-20 at 01:05 -0500, Albert Cahalan wrote:
> On 12/20/06, Mike Galbraith <efault@....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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/