John Baldwin 599afe53a8 Move NAME_MAX, LINK_MAX, and CHOWN_RESTRICTED out of vop_stdpathconf(). ... Having all filesystems fall through to default values isn't always correct and these values can vary for different filesystem implementations. Most of these changes just use the existing default values with a few exceptions: - Don't report CHOWN_RESTRICTED for ZFS since it doesn't do the exact permissions check this claims for chown(). - Use NANDFS_NAME_LEN for NAME_MAX for nandfs. - Don't report a LINK_MAX of 0 on smbfs. Now fail with EINVAL to indicate hard links aren't supported. Requested by: bde (though perhaps not this exact implementation) Reviewed by: kib (earlier version) MFC after: 1 month Sponsored by: Chelsio Communications		2017-12-19 19:51:36 +00:00
..
smbfs_io.c	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
smbfs_node.c	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
smbfs_node.h	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
smbfs_smb.c	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
smbfs_subr.c	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
smbfs_subr.h	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
smbfs_vfsops.c	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
smbfs_vnops.c	Move NAME_MAX, LINK_MAX, and CHOWN_RESTRICTED out of vop_stdpathconf().	2017-12-19 19:51:36 +00:00
smbfs.h	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00