Rick Macklem 13c581fc54 If the VOP_SETATTR() call that saves the exclusive create verifier failed, ... the NFS server would leave the newly created vnode locked. This could result in a file system that would not unmount and processes wedged, waiting for the file to be unlocked. Since this VOP_SETATTR() never fails for most file systems, this bug doesn't normally manifest itself. I found it during testing of an exported GlusterFS file system, which can fail. This patch adds the vput() and changes the error to the correct NFS one. MFC after: 2 weeks		2016-04-12 20:23:09 +00:00
..
nfs_fha_new.c	Fix RPC server threads file handle affinity to work better with ZFS.	2013-12-23 08:43:16 +00:00
nfs_fha_new.h	Revamp the old NFS server's File Handle Affinity (FHA) code so that	2013-04-17 21:00:22 +00:00
nfs_nfsdcache.c	Merge the NFSv4.1 server code in projects/nfsv4.1-server over	2014-07-01 20:47:16 +00:00
nfs_nfsdkrpc.c	When the nfsd threads are terminated, the NFSv4 server state	2015-11-21 23:55:46 +00:00
nfs_nfsdport.c	If the VOP_SETATTR() call that saves the exclusive create verifier failed,	2016-04-12 20:23:09 +00:00
nfs_nfsdserv.c	Cleanup unnecessary semicolons from the kernel.	2016-04-10 23:07:00 +00:00
nfs_nfsdsocket.c	Cleanup unnecessary semicolons from the kernel.	2016-04-10 23:07:00 +00:00
nfs_nfsdstate.c	When the nfsd threads are terminated, the NFSv4 server state	2015-11-21 23:55:46 +00:00
nfs_nfsdsubs.c	Cleanup unnecessary semicolons from the kernel.	2016-04-10 23:07:00 +00:00