From owner-freebsd-bugs Wed Jan 9 19:39:23 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id C3EC137B416 for ; Wed, 9 Jan 2002 19:39:18 -0800 (PST) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id OAA92556; Thu, 10 Jan 2002 14:39:11 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (localhost [127.0.0.1]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id OAA28995; Thu, 10 Jan 2002 14:39:11 +1100 (EST) Message-Id: <200201100339.OAA28995@lightning.itga.com.au> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 From: Gregory Bond To: "Ted Mittelstaedt" Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/33637: Panic: vm_page_unwire: invalid wire count: 0 In-reply-to: Your message of Wed, 09 Jan 2002 04:30:02 -0800. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Jan 2002 14:39:10 +1100 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Any application is able to cause a kernel panic with just regular library > calls. With respect to Ted, no non-root userland program should be able to panic the kernel. Ever. Yes, I know about fork-bombs, and malloc-bombs, and that login.conf can stop them, but they should still never panic the kernel. That they do (did?) in FreeBSD is still a (hard-to-fix) bug with a well-known workaround, not an acceptance of the fact that panics are acceptable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message