From owner-freebsd-hackers Fri Feb 13 17:01:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22413 for freebsd-hackers-outgoing; Fri, 13 Feb 1998 17:01:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22394 for ; Fri, 13 Feb 1998 17:01:00 -0800 (PST) (envelope-from Tor.Egge@idi.ntnu.no) Received: from idi.ntnu.no (tegge@presis.idi.ntnu.no [129.241.111.173]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id CAA27177; Sat, 14 Feb 1998 02:00:55 +0100 (MET) Message-Id: <199802140100.CAA27177@pat.idi.ntnu.no> To: rhh@ct.picker.com Cc: hackers@FreeBSD.ORG Subject: Re: "mount /dev/fd0 /" == REBOOT! (?) In-Reply-To: Your message of "Fri, 13 Feb 1998 16:42:31 -0500" References: <19980213164231.23272@ct.picker.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 14 Feb 1998 02:00:49 +0100 From: Tor Egge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > mount /dev/fd0 / > > I was surprised when the above command rebooted my machine. Is this > correct behavior? This is on 3.0-971208-SNAP BTW. This is a known problem (assuming that you got a panic: lockmgr: locking against myself). The mount system call has an exclusive lock on '/' while ffs_mount tries to perform a lookup on '/dev/rfd0'. PR kern/434, kern/1031, kern/1067, kern/2174 reports the same problem. I've sent a suggested fix for PR#1067. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message