From owner-freebsd-hackers Mon Dec 13 22:11:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id A296214ED0 for ; Mon, 13 Dec 1999 22:11:35 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id QAA01791; Tue, 14 Dec 1999 16:41:26 +1030 (CST) (envelope-from newton) Date: Tue, 14 Dec 1999 16:41:26 +1030 From: Mark Newton To: mauzi@poli.hu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: umount -f causes page fault in kernel? Message-ID: <19991214164126.C1587@internode.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 13, 1999 at 04:27:48PM +0100, Gergely EGERVARY wrote: [ ... ] "Doctor, it hurts when I do this:" > mount /cdrom > cd /cdrom > umount -f /cdrom > cd .. > will cause 100% reproduceable kernel panic (page fault) "So don't do that then!" > I know forced umount is dangerous, but soo ... =P It's described as "dangerous" precisely because it causes a kernel panic. Why on earth would you want/need to do that anyway? - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message