sommerfe 36dc99adac vinvalbuf, called from vclean, could cause a locking-against-self ... deadlock in VOP_FSYNC() if the unreferenced vnode picked for reclamation happened to be stacked on top of a vnode the process already had locked. This could happen if the same filesystem was accessed both through a union mount and directly; it seemed to happen most frequently when the direct access was through NFS. Avoid this deadlock by changing vinvalbuf to pass a new FSYNC_RECLAIM flag bit to VOP_FSYNC() to indicate that a reclaim is in progress and only a `shallow' fsync is necessary. Do nothing in *_fsync() in umapfs, nullfs, and unionfs when FSYNC_RECLAIM is set; the underlying vnodes will shortly be released in *_reclaim and may be reclaimed (and fsync'ed) later.		1999-03-22 17:24:19 +00:00
..
Makefile	Rework the way kernel include files are installed. In the new method,	1998-06-12 23:22:30 +00:00
umap.h	Merge with Lite2 + local changes	1998-03-01 02:20:01 +00:00
umap_subr.c	Apply patch from kern/5538:	1999-03-19 21:46:25 +00:00
umap_vfsops.c	Apply patch from kern/5538:	1999-03-19 21:46:25 +00:00
umap_vnops.c	vinvalbuf, called from vclean, could cause a locking-against-self	1999-03-22 17:24:19 +00:00