From owner-freebsd-current Thu Mar 29 2:38:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 5DEE237B71E; Thu, 29 Mar 2001 02:38:39 -0800 (PST) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id CAA18451; Thu, 29 Mar 2001 02:38:34 -0800 (PST) (envelope-from DougB@DougBarton.net) Message-ID: <3AC310AA.EA852DEC@DougBarton.net> Date: Thu, 29 Mar 2001 02:38:34 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: John Baldwin , Terry Lambert , current@FreeBSD.ORG Subject: Re: Fun way to panic -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > On Wed, 28 Mar 2001, John Baldwin wrote: > > > On 28-Mar-01 Terry Lambert wrote: > > > Run the 4.3 mountd on it. > > > > > > Boom! Kernel memory allocation way to large; unrecoverable! > > Does this really panic -current? It panics old versions of -current, and > the -current mountd panics RELENG_4, but current versions of -current are > supposed to check the parameters passwd by mountd (etc.) enough to avoid > the panic. FYI, running releng_4 mountd on a releng_3 system also fails in a fairly spectacular fashion... occasionally panic'ing the system. Doug -- Perhaps the greatest damage the American system of education has done to its children is to teach them that their opinions are relevant simply because they are their opinions. Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message