NetBSD/sys/miscfs/nullfs
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
null.h
null_subr.c Workaropund fix for PR #5239 from <minoura@kw.netlaputa.ne.jp>: 1998-09-30 06:50:10 +00:00
null_vfsops.c Modify vfsops to seperate vfs_fhtovp() into two routines. vfs_fhtovp() now 1999-02-26 23:44:43 +00:00
null_vnops.c vinvalbuf, called from vclean, could cause a locking-against-self 1999-03-22 17:24:19 +00:00