Date: Fri, 23 Oct 1998 01:29:01 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: Doug Rabson <dfr@nlsystems.com>, Terry Lambert <tlambert@primenet.com> Cc: current@FreeBSD.ORG Subject: Re: -current NFS problem Message-ID: <199810230829.BAA20382@salsa.gv.tsc.tdk.com> In-Reply-To: Doug Rabson <dfr@nlsystems.com> "Re: -current NFS problem" (Oct 20, 9:01am)
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 20, 9:01am, Doug Rabson wrote: } Subject: Re: -current NFS problem } On Tue, 20 Oct 1998, Terry Lambert wrote: } > My main question would be: } > } > o Do you see any reason why nfsnode locking should be necessary? } } The last time I spoke to Rick about this, he said that the reason NFS } can't use a vnode lock is to prevent a server hang from causing a lock } cascade ending up with the root vnode being locked and the whole machine } wedged. I experimented for a while with a gross hack which only locked } regular files but it was too complicated and I ditched it. Hmn, as another gross hack, how about unlocking the parent directory before locking the child when crossing a mount point? You'd have to disallow operations at the mount point that want namei() to return with the parent locked, but this doesn't look like it would be much of a loss. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810230829.BAA20382>