NetBSD Problem Report #767

From gnats  Sun Jan 29 18:58:19 1995
Received: from pain.lcs.mit.edu (pain.lcs.mit.edu [128.52.46.239]) by sun-lamp.cs.berkeley.edu (8.6.9/8.6.9) with ESMTP id SAA06422 for <gnats-bugs@sun-lamp.cs.berkeley.edu>; Sun, 29 Jan 1995 18:58:19 -0800
Message-Id: <199501300258.SAA00689@lust.cs.utk.edu>
Date: Sun, 29 Jan 1995 18:58:40 -0800
From: moore@cs.utk.edu
Reply-To: moore@lust.cs.utk.edu
To: gnats-bugs@NetBSD.ORG
Subject: another case of "panic: ufs_unlock NOT LOCKED"
X-Send-Pr-Version: 3.2

>Number:         767
>Category:       kern
>Synopsis:       mounting via NFS over some process's cwd causes panic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 29 19:05:08 +0000 1995
>Closed-Date:    Mon Dec 07 14:44:33 +0000 1998
>Last-Modified:  Mon Dec 07 14:45:17 +0000 1998
>Originator:     Keith Moore
>Release:        1.0
>Organization:
"none"
>Environment:
sparcstation1, netbsd-1.0

System: NetBSD lust.cs.utk.edu 1.0 NetBSD 1.0 (SPARC_SCSI3) #0: Mon Oct 24 15:23:27 MDT 1994 deraadt@croc:/croc.usera/rel/src/sys/arch/sparc/compile/SPARC_SCSI3 sparc


>Description:
	(this appears to be the same bug as kern/498...this is just
	another data point)
	if you mount a remote NFS filesystem over someone's current
	directory, the kernel will panic when that person tries to
	access that directory (underneath the mount).

>How-To-Repeat:
	cd /some/directory
	mount remote-host:/foo /some/directory
	ls

>Fix:
	On the UNIX systems I'm used to, this could not happen because mount
	(2) would return EBUSY.  My guess is that this is really a problem 
	with mount() not doing enough checking for this case.
>Release-Note:
>Audit-Trail:

From: mouse@NetBSD.ORG
To: moore@cs.utk.edu
Cc: gnats-bugs@NetBSD.ORG
Subject: Re: kern/767: another case of "panic: ufs_unlock NOT LOCKED"
Date: Wed, 2 Dec 1998 09:34:26 -0500 (EST)

 I tried to reproduce this on a 1.3F NetBSD/sparc system and couldn't.
 Do you still see it?  If not, I'll be happy to close it out as fixed.

 					der Mouse

 				     mouse@netbsd.org
 			       mouse@rodents.montreal.qc.ca
 		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

From: Keith Moore <moore@cs.utk.edu>
To: mouse@NetBSD.ORG
Cc: moore@cs.utk.edu, gnats-bugs@NetBSD.ORG
Subject: Re: kern/767: another case of "panic: ufs_unlock NOT LOCKED" 
Date: Wed, 02 Dec 1998 09:51:14 -0500

 > I tried to reproduce this on a 1.3F NetBSD/sparc system and couldn't.
 > Do you still see it?  If not, I'll be happy to close it out as fixed.

 That bug was one I noticed essentially by accident.  I haven't
 observed it since then, but I haven't tried to exercise it either.

 If memory serves, when I posted the bug report I also provided an 
 example of how to exercise the bug.  If you've tried to do so by 
 following the example, and the bug no longer occurs, I would 
 declare the bug to be fixed.

 Keith
State-Changed-From-To: open->closed 
State-Changed-By: mouse 
State-Changed-When: Mon Dec 7 06:44:33 PST 1998 
State-Changed-Why:  
Appears to be fixed (see audit-trail email exchange with submitter). 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.