From owner-freebsd-current Wed Apr 2 12:40:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA22607 for current-outgoing; Wed, 2 Apr 1997 12:40:27 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA22581; Wed, 2 Apr 1997 12:40:03 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA14329; Wed, 2 Apr 1997 13:16:38 -0700 From: Terry Lambert Message-Id: <199704022016.NAA14329@phaeton.artisoft.com> Subject: Re: ufs lock panic in -current To: karl@Mcs.Net (Karl Denninger) Date: Wed, 2 Apr 1997 13:16:38 -0700 (MST) Cc: terry@lambert.org, ache@nagual.ru, dyson@FreeBSD.ORG, bde@zeta.org.au, current@FreeBSD.ORG In-Reply-To: <19970402131508.59503@Jupiter.Mcs.Net> from "Karl Denninger" at Apr 2, 97 01:15:08 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Am I correct in understanding that this isn't fixed yet, and that also the > NFS exec() problems with paging are also still open? Yes. I believe, however, that Doug Rabson was replacing the stubbed routines in the NFS case to respect the lock used by vclean. This is a sort of kludge soloution, but should fix the NFS vnode problems. The paging problems were mentioned by John Dyson as something he was actively looking at; they are, it seems, related to the VM object alising issues that the Lite2 unionfs also suffers under (from my minimal reading of John's posting and the affected code in both FS's). > I'm sorry about not being more up-to-date on this; I've been INSANELY busy > the last few weeks, and haven't had time to dig into the NFS layer. Is it > still as it was? > > (BTW, its easy to test -- a loopback mount from the same machine will fail > just as hard as one over a real wire). I believe the work discussed above may be sufficient to mask both these problems (and solve them, in one of the cases). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.