KATO Takenori 9095719e2b Quick-hack to avoid `lock against myself' panic. It is not the real ... fix! The ufs_link() assumes that vnode is not unlocked and tries to lock it in certain case. Because union_link calls VOP_LINK after locking vnode, vn_lock in ufs_link causes above panic. Currently, I don't know the real fix for a locking violation in union_link, but I think it is important to avoid panic. A vnode is unlocked before calling VOP_LINK and is locked after it if the vnode is not union fs. Even though panic went away, the process that access the union fs in which link was made will hang-up. Hang-up can be easily reproduced by following operation: mount -t union a b cd b ln foo bar ls		1997-04-15 12:56:57 +00:00
..
union_subr.c	The path name buffer, cn->cn_pnbuf, is FREEed by VOP_MKDIR when	1997-04-13 06:27:09 +00:00
union_vfsops.c	Fix `lockmgr: locking against myself' panic by multi union mount of	1997-04-14 10:52:25 +00:00
union_vnops.c	Quick-hack to avoid `lock against myself' panic. It is not the real	1997-04-15 12:56:57 +00:00
union.h	Back out part 1 of the MCFH that changed $Id$ to $FreeBSD$. We are not	1997-02-22 09:48:43 +00:00