Conrad Meyer b5af3f30a7 nfsclient: Protest loudly when GETATTR responses are invalid ... BROKEN NFS SERVER OR MIDDLEWARE: Certain WAN "accelerators" attempt to cache NFS GETATTR traffic, but actually corrupt it (e.g., responding to requests with attributes for totally different files). Warn very verbosely when this is detected. Linux' NFS client has a similar warning. Adds a sysctl/tunable (vfs.nfs.fileid_maxwarnings) to configure the quantity of warnings; default to 10. (Zero disables; -1 is unlimited.) Adds a failpoint to aid in validating the warning / behavior with a non-broken server. Use something like: sysctl 'debug.fail_point.nfscl_force_fileid_warning=10%return(1)' Reviewed by: rmacklem Approved by: markj (mentor) Sponsored by: EMC / Isilon Storage Division Differential Revision: https://reviews.freebsd.org/D3304		2015-08-05 22:27:30 +00:00
..
nfs_clbio.c	o Un-inline vm_pager_get_pages(), vm_pager_get_pages_async().	2015-06-17 22:44:27 +00:00
nfs_clcomsubs.c
nfs_clkdtrace.c
nfs_clkrpc.c
nfs_clnfsiod.c
nfs_clnode.c
nfs_clport.c	nfsclient: Protest loudly when GETATTR responses are invalid	2015-08-05 22:27:30 +00:00
nfs_clrpcops.c	Alex Burlyga reported a POLA violation for the new NFS client as	2015-07-03 01:15:21 +00:00
nfs_clstate.c
nfs_clsubs.c
nfs_clvfsops.c	If a "principal" argument isn't provided for a Kerberized NFS mount,	2015-07-03 22:11:07 +00:00
nfs_clvnops.c
nfs_kdtrace.h
nfs.h
nfsmount.h
nfsnode.h
nlminfo.h