From owner-freebsd-bugs  Sat May 25 19:30:09 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA27260
          for bugs-outgoing; Sat, 25 May 1996 19:30:09 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA27254;
          Sat, 25 May 1996 19:30:06 -0700 (PDT)
Resent-Date: Sat, 25 May 1996 19:30:06 -0700 (PDT)
Resent-Message-Id: <199605260230.TAA27254@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, brion@queeg.com
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
X-Send-Pr-Version: 3.2
Subject: kern/1250: chroot to nullfs causes kernel panic
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         1250
>Category:       kern
>Synopsis:       chroot to nullfs causes kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 25 19:30:03 PDT 1996
>Last-Modified:
>Originator:     Brion Moss
>Organization:
NetDaemons Associates
>Release:        FreeBSD 2.1-STABLE i386
>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:
	
>Audit-Trail:
>Unformatted: