From brion@coven.queeg.com  Sat May 25 19:22:10 1996
Received: from coven.queeg.com (queeg.com [204.95.70.218])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA26909
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 25 May 1996 19:22:08 -0700 (PDT)
Received: (from brion@localhost) by coven.queeg.com (8.7.4/8.7.1) id SAA00392; Sat, 25 May 1996 18:53:59 -0700 (PDT)
Message-Id: <199605260153.SAA00392@coven.queeg.com>
Date: Sat, 25 May 1996 18:53:59 -0700 (PDT)
From: Brion Moss <brion@queeg.com>
Reply-To: brion@queeg.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: chroot to nullfs causes kernel panic
X-Send-Pr-Version: 3.2

>Number:         1250
>Category:       kern
>Synopsis:       chroot to nullfs causes kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 25 19:30:03 PDT 1996
>Closed-Date:    Mon May 27 14:26:00 PDT 1996
>Last-Modified:  Mon May 27 14:30:24 PDT 1996
>Originator:     Brion Moss
>Release:        FreeBSD 2.1-STABLE i386
>Organization:
NetDaemons Associates
>Environment:

	FreeBSD 2.1.0-RELEASE
	Pentium 133 w/Triton chipset

>Description:

	I am setting up a web server in a chrooted enviroment.  I had
	been using NFS to remount the web directories read-only, and
	then chrooted to the NFS mount point, but when I learned of the
	lofs and null filesystem types, I decided to try using them instead.
	Since my system doesn't seem to support lofs, I tried null.
	I could reliably halt the system by chrooting to the null
	mount point, regardless of the command.  The error I got was:

		Fatal trap 18: integer divide fault while in kernel mode
		Instruction pointer 0x8:0xf0195a5f
		Code segment base 0x0, limit 0xfffff, type 0x1b,
			DPL 0, pres 1, def32 1, gran 1

>How-To-Repeat:

	mount -t null /bin /mnt
	chroot /mnt /date

>Fix:
	
>Release-Note:
>Audit-Trail:

From: J Wunsch <j@uriah.heep.sax.de>
To: brion@queeg.com
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/1250: chroot to nullfs causes kernel panic
Date: Sun, 26 May 1996 10:50:44 +0200 (MET DST)

 As Brion Moss wrote:
 > 
 > >Number:         1250
 > >Category:       kern
 > >Synopsis:       chroot to nullfs causes kernel panic
 
 nullfs is known to be broken.
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)
State-Changed-From-To: open->closed 
State-Changed-By: gpalmer 
State-Changed-When: Mon May 27 14:26:00 PDT 1996 
State-Changed-Why:  
Basically a duplicate of PR #34. Nullfs is known to be broken, 
especially for writes. 
>Unformatted:
