Rick Macklem 262a84286d The NFS client generated directory block(s) with d_fileno == 0 ... so that it would not return less data than requested. Since returning less directory data than requested is not a problem for FreeBSD and even UFS no longer returns directory structures with d_fileno == 0, this patch stops the client from doing this. Although entries with d_fileno == 0 should not be a problem, the man pages no longer document that these entries should be ignored, so there was a concern that these entries might be an issue in the future. Suggested by: trasz Tested by: trasz MFC after: 2 weeks		2015-05-23 21:58:41 +00:00
..
autofs
cd9660
cuse
deadfs
devfs	Refine r280308. Do not completely disable timestamping of devfs nodes	2015-04-01 08:25:40 +00:00
ext2fs	Drop experimental dir_index support.	2015-04-17 22:26:01 +00:00
fdescfs
fifofs
fuse	File systems that do not use the buffer cache (such as ZFS) must	2015-04-15 20:16:31 +00:00
msdosfs	File systems that do not use the buffer cache (such as ZFS) must	2015-04-15 20:16:31 +00:00
nandfs	File systems that do not use the buffer cache (such as ZFS) must	2015-04-15 20:16:31 +00:00
nfs	CALLOUT_MPSAFE has lost its meaning since r141428, i.e., for more than ten	2015-05-22 17:05:21 +00:00
nfsclient	The NFS client generated directory block(s) with d_fileno == 0	2015-05-23 21:58:41 +00:00
nfsserver	Fix the NFS server's handling of a bogus NFSv2 ROOT RPC.	2015-04-25 00:58:24 +00:00
nullfs	File systems that do not use the buffer cache (such as ZFS) must	2015-04-15 20:16:31 +00:00
procfs	Always set p_oppid when attaching to an existing process via procfs	2015-05-22 11:03:51 +00:00
pseudofs
smbfs
tmpfs	tmpfs_getattr(): Return more correct allocated byte counts.	2015-04-10 19:04:39 +00:00
udf
unionfs