From owner-freebsd-stable@FreeBSD.ORG  Fri Sep  1 19:07:39 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: 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 E8C3C16A4DA;
	Fri,  1 Sep 2006 19:07:39 +0000 (UTC) (envelope-from vovk@km.ua)
Received: from fido.km.ua (fido.km.ua [195.46.36.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1B84343D58;
	Fri,  1 Sep 2006 19:07:38 +0000 (GMT) (envelope-from vovk@km.ua)
Received: from [10.0.0.8] (id.km.ua [195.46.36.18]) (authenticated bits=0)
	by fido.km.ua (8.13.6/8.13.6/add-fido.auth) with ESMTP id
	k81J7SjH026337; Fri, 1 Sep 2006 22:07:29 +0300 (EEST)
	(envelope-from vovk@km.ua)
Date: Fri, 1 Sep 2006 22:07:57 +0300
From: Vyacheslav Vovk <vovk@km.ua>
X-Mailer: The Bat! (v3.81.06 Beta) Professional
X-Priority: 3 (Normal)
Message-ID: <1154543100.20060901220757@km.ua>
To: Julian Elischer <julian@elischer.org>
In-Reply-To: <44F85F63.5020508@elischer.org>
References: <200609011716.30749.vovk@km.ua> <44F85F63.5020508@elischer.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new
Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org
Subject: Re[2]: panic: vm_thread_new: kstack allocation failed
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Vyacheslav Vovk <vovk@km.ua>
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, 01 Sep 2006 19:07:40 -0000

Hello Julian,

Friday, September 1, 2006, 7:27:15 PM, you wrote:

> Vyacheslav Vovk wrote:

> can you see how many threads thre are in the system?
> I think you will have to extract this information frome the zone allocator.

how to do it practically?

> I just realised there is no effective limit on kernel threads in the system.
> probably one could cause this with a fork bomb appoach using forks and
> thread creation.

what can be staying in this fork bomb?

-- 
wbr, slava [vovk-uanic]