Konstantin Belousov 57bfe0a9f8 Do not fork nfsiod directly from the vop methods. This causes LORs between ... vnode lock and several locks needed during fork, like fd lock. Instead, schedule the task to be executed in the taskqueue context. We still waiting for the fork to finish, but the context of the thread executing the task does not make real LORs with our vnode lock. Submitted by: pluknet at gmail com Reviewed by: jhb Tested by: pho MFC after: 3 weeks		2010-09-12 19:06:08 +00:00
..
bootp_subr.c
krpc_subr.c
krpc.h
nfs_bio.c
nfs_diskless.c
nfs_kdtrace.c
nfs_kdtrace.h
nfs_krpc.c
nfs_nfsiod.c	Do not fork nfsiod directly from the vop methods. This causes LORs between	2010-09-12 19:06:08 +00:00
nfs_node.c
nfs_subs.c	Do not fork nfsiod directly from the vop methods. This causes LORs between	2010-09-12 19:06:08 +00:00
nfs_vfsops.c
nfs_vnops.c	Store the full timestamp when caching timestamps of files and	2010-09-07 14:29:45 +00:00
nfs.h	Do not fork nfsiod directly from the vop methods. This causes LORs between	2010-09-12 19:06:08 +00:00
nfsargs.h
nfsdiskless.h
nfsm_subs.h
nfsmount.h
nfsnode.h	Store the full timestamp when caching timestamps of files and	2010-09-07 14:29:45 +00:00
nfsstats.h
nlminfo.h