- Replace the series of DEBUG_LOCKS hacks which tried to save the vn_lock

   caller by saving the stack of the last locker/unlocker in lockmgr.  We
   also put the stack in KTR at the moment.

Contributed by:		Antoine Brodin <antoine.brodin@laposte.net>

1 files changed, 0 insertions, 12 deletions

diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c
index 3337e10..d8c00fd 100644
--- a/sys/kern/vfs_vnops.c
+++ b/sys/kern/vfs_vnops.c
@@ -779,18 +779,10 @@ vn_poll(fp, events, active_cred, td)
  * acquire requested lock.
  */
 int
-#ifndef	DEBUG_LOCKS
 vn_lock(vp, flags, td)
-#else
-debug_vn_lock(vp, flags, td, filename, line)
-#endif
 	struct vnode *vp;
 	int flags;
 	struct thread *td;
-#ifdef	DEBUG_LOCKS
-	const char *filename;
-	int line;
-#endif
 {
 	int error;
 
@@ -809,10 +801,6 @@ debug_vn_lock(vp, flags, td, filename, line)
 			VI_UNLOCK(vp);
 			return (0);
 		}
-#ifdef	DEBUG_LOCKS
-		vp->filename = filename;
-		vp->line = line;
-#endif
 		/*
 		 * lockmgr drops interlock before it will return for
 		 * any reason.  So force the code above to relock it.