From owner-freebsd-stable@FreeBSD.ORG Sun Mar 12 02:52:00 2006 Return-Path: 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 DB0C316A422; Sun, 12 Mar 2006 02:52:00 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15CEE456A7; Sun, 12 Mar 2006 00:34:16 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from localhost.my.domain (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2C0YEEl044042; Sun, 12 Mar 2006 00:34:15 GMT (envelope-from davidxu@freebsd.org) From: David Xu To: freebsd-threads@freebsd.org, Martin , freebsd-stable@freebsd.org Date: Sun, 12 Mar 2006 08:29:18 +0800 User-Agent: KMail/1.8.2 References: <200603111140.k2BBerFh096411@freefall.freebsd.org> In-Reply-To: <200603111140.k2BBerFh096411@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603120829.18291.davidxu@freebsd.org> Cc: Subject: Re: threads/80435: panic on high loads X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 02:52:01 -0000 [stable is included] On Saturday 11 March 2006 19:40, Martin wrote: > > The following reply was made to PR threads/80435; it has been noted by GNATS. > > From: Martin > To: bug-followup@FreeBSD.org > Cc: > Subject: Re: threads/80435: panic on high loads > Date: Sat, 11 Mar 2006 12:36:04 +0100 > > Hi, > > I've a similar panic. Not exactly the same, but in a similar > situation. You can trigger it with a slightly modified fork bomb: > > #include > #include > > int main(void) > { > while(1) { > fork(); > malloc(1024); > } > return 0; > } > > > The resulting panic is: > > fault code = supervisor write, page not present > > backtrace: > pmap_qenter() > vm_thread_new() > thread_init() > slab_zalloc() > uma_zone_slab() > uma_zalloc_bucket() > uma_zalloc_arg() > thread_alloc() > proc_init() > slab_zalloc() > uma_zone_slab() > uma_zalloc_bucket() > uma_zalloc_arg() > fork1() > fork() > syscall() > Xint0x80() > -- syscall (2, FreeBSD ELF32, fork) > > Reproducible on: -STABLE > uname -a: > FreeBSD klotz.local 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Mon Mar 6 > 00:21:54 CET 2006 root@klotz.local:/usr/obj/usr/src/sys/KLOTZ i386 > > -- > Martin This bug unlikely should be reported on thread@, your code is a fork bomb, I think it is a warning why recent days the kernel crashed by such attack, can you reproduce it on 6.0 ? David Xu