> I agree that the train-wreck behavior of the current vnode locking design
> is poor, but that's how it is.  if you want to avoid that, we should discuss
> changing the vnode locking design such it doesn't have that problem.
> the SVR4 vnode locking design would be a good place to start, since it
> doesn't intrinsically have this problem.

do you have any pointer to description of SVR4 locking design?

YAMAMOTO Takashi