Rick Macklem ae03cbd7f3 Allow the NFSv4 server to reply NFSERR_WRONGSEC for the SetClientID operation. ... It was reported via email that a Linux client couldn't do a Kerberized NFS mount when only "sec=krb5" was specified for the exports. The Linux client attempted a mount via krb5i and the server replied NFSERR_SERVERFAULT. Although NFSERR_WRONGSEC isn't listed as an error for SetClientID, I think it is the correct reply, so this patch enables that. I do not know if this fixes the mount attempt, but adding "krb5i" to the list of allowed security flavours does allow the mount to work. Reported by: joef@spectralogic.com MFC after: 2 weeks		2016-04-23 21:18:45 +00:00
..
nfs_fha_new.c
nfs_fha_new.h
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	Fix a LOR in the NFSv4.1 server.	2016-04-23 01:22:04 +00:00
nfs_nfsdsubs.c	Allow the NFSv4 server to reply NFSERR_WRONGSEC for the SetClientID operation.	2016-04-23 21:18:45 +00:00