From owner-freebsd-fs Sun Oct 25 03:06:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28997 for freebsd-fs-outgoing; Sun, 25 Oct 1998 03:06:26 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from elixir.e.kth.se (elixir.e.kth.se [130.237.48.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28978; Sun, 25 Oct 1998 03:06:21 -0800 (PST) (envelope-from lha@s3.kth.se) Received: from zinfandel.e.kth.se (1073744992@zinfandel.e.kth.se [130.237.48.172]) by elixir.e.kth.se (8.8.7/8.8.7) with ESMTP id MAA19263; Sun, 25 Oct 1998 12:05:45 +0100 (MET) Received: (lha@localhost) by zinfandel.e.kth.se (8.8.7/8.6.6) id MAA03108; Sun, 25 Oct 1998 12:05:44 +0100 (MET) To: Michael Hancock Cc: freebsd-fs@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, kom-arla@stacken.kth.se Subject: Re: deadfs in FreeBSD 3.0/current ? References: From: Love Date: 25 Oct 1998 12:05:44 +0100 In-Reply-To: Michael Hancock's message of Sun, 25 Oct 1998 18:53:50 +0900 (JST) Message-ID: Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Hancock writes: > On Sun, 25 Oct 1998, Love wrote: > > > 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 ? > > > > The wakeup at the bottom of vclean()? That code also clears VXLOCK. But that is done *after* the tsleep, and therefor that code will *never* be reached. Kind of hard to wake yourself up. It will hang in miscfs/deadfs/dead_vnops.c(1.24):240 forever. Love To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message