From owner-freebsd-bugs  Thu Jun  1 18:40:02 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id SAA21631
          for bugs-outgoing; Thu, 1 Jun 1995 18:40:02 -0700
Received: (from gnats@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id SAA21624
          ; Thu, 1 Jun 1995 18:40:01 -0700
Date: Thu, 1 Jun 1995 18:40:01 -0700
Message-Id: <199506020140.SAA21624@freefall.cdrom.com>
From: Stephen McKay <syssgm@devetir.qld.gov.au>
Reply-To: Stephen McKay <syssgm@devetir.qld.gov.au>
To: freebsd-bugs
Subject: kern/472: bad mount causes panic: ufs_lock
In-Reply-To: Your message of Fri, 2 Jun 1995 11:06:11 +1000
	<199506020106.LAA00224@stupid.devetir.qld.gov.au>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         472
>Category:       kern
>Synopsis:       'mount /foo /foo' causes panic: ufs_lock
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jun  1 18:40:00 1995
>Originator:     Stephen McKay
>Organization:
>Release:        FreeBSD 2.0-BUILT-19950510 i386
>Environment:

	386SX16 4Mb ram, IDE 80Mb, 10Mb swap
	FreeBSD-current CTM src-cur 681 (1995-05-31 01:19:48)
	Perhaps you think of this as 2.0.5-ALPHA.

>Description:

	One hazy afternoon, I mistyped a floppy mount command and got:

	    mount -t msdos /fd0 /fd0

	Result:

	    panic: ufs_lock: recursive lock not expected, pid: 267

	To be sure of this, I rebooted and tried:

	    mount /fd0 /fd0

	Result:

	    panic: ufs_lock: recursive lock not expected, pid: 11


>How-To-Repeat:

	'mount /mnt /mnt' should do the trick.

>Fix:
	
	Unknown.
>Audit-Trail:
>Unformatted: