From owner-freebsd-stable@FreeBSD.ORG  Thu Aug 14 20:15:18 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id A838537B401; Thu, 14 Aug 2003 20:15:18 -0700 (PDT)
Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su
	[213.184.65.80])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C29DA43F93; Thu, 14 Aug 2003 20:15:16 -0700 (PDT)
	(envelope-from eugen@kuzbass.ru)
Received: from kuzbass.ru (kost [213.184.65.82])h7F3FDel051496;
	Fri, 15 Aug 2003 11:15:13 +0800 (KRAST)
	(envelope-from eugen@kuzbass.ru)
Message-ID: <3F3C5017.B1A20E16@kuzbass.ru>
Date: Fri, 15 Aug 2003 11:14:31 +0800
From: Eugene Grosbein <eugen@kuzbass.ru>
Organization: SVZServ
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: ru,en
MIME-Version: 1.0
To: Doug White <dwhite@gumbysoft.com>
References: <20030815003035.A32998@grosbein.pp.ru>
	<20030814110321.V4145@carver.gumbysoft.com>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
cc: stable@freebsd.org
cc: bug-followup@freebsd.org
Subject: Re: bin/55346: /bin/sh eats memory and CPU infinitely
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Aug 2003 03:15:19 -0000

Doug White wrote:

> > It seems /bin/sh in 4.8-STABLE has problem with SIGCHLD processing.
> > In short, it often fails to process it correctly, zombies float
> > around, jobs are not marked as finished in jobtab[] that fills memory
> > and takes much CPU to be processed.
> >
> > Run this one-liner using /bin/sh and see hundreds of zombies:
> >
> > #!/bin/sh
> > while :; do : & done
> 
> Considering that with this script you are forkbombing your machine as
> root, I think this falls into the "doctor it hurts when I shoot my foot"
> category.

Perhaps. Anyway, debug shows that jobtab[] in /bin/sh grows indefinitely
in some scenarios and the reason should be SIGCHLD processing problem.

Eugene