Date: 25 Oct 1998 12:05:44 +0100 From: Love <lha@e.kth.se> To: Michael Hancock <michaelh@cet.co.jp> Cc: freebsd-fs@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, kom-arla@stacken.kth.se Subject: Re: deadfs in FreeBSD 3.0/current ? Message-ID: <am67d87vg7.fsf@zinfandel.e.kth.se> In-Reply-To: Michael Hancock's message of Sun, 25 Oct 1998 18:53:50 %2B0900 (JST) References: <Pine.BSF.3.95LJ1.1b3.981025185219.1008A-100000@sv01.cet.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Hancock <michaelh@cet.co.jp> 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-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?am67d87vg7.fsf>