From owner-freebsd-fs Sun Oct 25 01:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23951 for freebsd-fs-outgoing; Sun, 25 Oct 1998 01:53:53 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from sv01.cet.co.jp (sv01.cet.co.jp [210.171.56.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23933; Sun, 25 Oct 1998 01:53:51 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by sv01.cet.co.jp (8.8.8/8.8.8) with SMTP id JAA01021; Sun, 25 Oct 1998 09:53:50 GMT (envelope-from michaelh@cet.co.jp) Date: Sun, 25 Oct 1998 18:53:50 +0900 (JST) From: Michael Hancock To: Love cc: freebsd-fs@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, kom-arla@stacken.kth.se Subject: Re: deadfs in FreeBSD 3.0/current ? In-Reply-To: <199810250912.JAA05540@nutcracker.e.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The wakeup at the bottom of vclean()? That code also clears VXLOCK. Regards, Mike On Sun, 25 Oct 1998, Love wrote: > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message