Date: Sat, 25 May 1996 18:53:59 -0700 (PDT) From: Brion Moss <brion@queeg.com> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/1250: chroot to nullfs causes kernel panic Message-ID: <199605260153.SAA00392@coven.queeg.com> Resent-Message-ID: <199605260230.TAA27254@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605260153.SAA00392>