From owner-freebsd-fs  Sun Oct 25 01:15:23 1998
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA20934
          for freebsd-fs-outgoing; Sun, 25 Oct 1998 01:15:23 -0800 (PST)
          (envelope-from owner-freebsd-fs@FreeBSD.ORG)
Received: from nutcracker.e.kth.se (nutcracker.e.kth.se [130.237.43.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20929;
          Sun, 25 Oct 1998 01:15:16 -0800 (PST)
          (envelope-from lha@nutcracker.e.kth.se)
Received: (from lha@localhost)
	by nutcracker.e.kth.se (8.8.8/8.8.8) id JAA05540;
	Sun, 25 Oct 1998 09:12:55 GMT
	(envelope-from lha)
Date: Sun, 25 Oct 1998 09:12:55 GMT
Message-Id: <199810250912.JAA05540@nutcracker.e.kth.se>
From: Love <lha@s3.kth.se>
To: freebsd-fs@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, kom-arla@stacken.kth.se
Subject: deadfs in FreeBSD 3.0/current ?
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Hello

kern/vfs_subr.c:vclean() does a vp->v_flag |= VXLOCK; and after that
"calls" VOP_LOCK().

Now when the filesystem is deadfs (we use it in arla[1]), the call
ends up in miscfs/deadfs/dead_vnops.c:dead_lock() that calls
chkvnlock(). Now chkvnlock() sleeps when VXLOCK is set.

Who will wake us up ?

Love,
arla-drinker

[1] arla, a free afs-clone <http://www.stacken.kth.se/project/arla/>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message