Kconfig 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. config NFSD
  3. tristate "NFS server support"
  4. depends on INET
  5. depends on FILE_LOCKING
  6. depends on FSNOTIFY
  7. select CRC32
  8. select LOCKD
  9. select SUNRPC
  10. select EXPORTFS
  11. select NFS_COMMON
  12. select NFS_ACL_SUPPORT if NFSD_V2_ACL
  13. select NFS_ACL_SUPPORT if NFSD_V3_ACL
  14. depends on MULTIUSER
  15. help
  16. Choose Y here if you want to allow other computers to access
  17. files residing on this system using Sun's Network File System
  18. protocol. To compile the NFS server support as a module,
  19. choose M here: the module will be called nfsd.
  20. You may choose to use a user-space NFS server instead, in which
  21. case you can choose N here.
  22. To export local file systems using NFS, you also need to install
  23. user space programs which can be found in the Linux nfs-utils
  24. package, available from http://linux-nfs.org/. More detail about
  25. the Linux NFS server implementation is available via the
  26. exports(5) man page.
  27. Below you can choose which versions of the NFS protocol are
  28. available to clients mounting the NFS server on this system.
  29. Support for NFS version 3 (RFC 1813) is always available when
  30. CONFIG_NFSD is selected.
  31. If unsure, say N.
  32. config NFSD_V2
  33. bool "NFS server support for NFS version 2 (DEPRECATED)"
  34. depends on NFSD
  35. default n
  36. help
  37. NFSv2 (RFC 1094) was the first publicly-released version of NFS.
  38. Unless you are hosting ancient (1990's era) NFS clients, you don't
  39. need this.
  40. If unsure, say N.
  41. config NFSD_V2_ACL
  42. bool "NFS server support for the NFSv2 ACL protocol extension"
  43. depends on NFSD_V2
  44. config NFSD_V3_ACL
  45. bool "NFS server support for the NFSv3 ACL protocol extension"
  46. depends on NFSD
  47. help
  48. Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
  49. never became an official part of the NFS version 3 protocol.
  50. This protocol extension allows applications on NFS clients to
  51. manipulate POSIX Access Control Lists on files residing on NFS
  52. servers. NFS servers enforce POSIX ACLs on local files whether
  53. this protocol is available or not.
  54. This option enables support in your system's NFS server for the
  55. NFSv3 ACL protocol extension allowing NFS clients to manipulate
  56. POSIX ACLs on files exported by your system's NFS server. NFS
  57. clients which support the Solaris NFSv3 ACL protocol can then
  58. access and modify ACLs on your NFS server.
  59. To store ACLs on your NFS server, you also need to enable ACL-
  60. related CONFIG options for your local file systems of choice.
  61. If unsure, say N.
  62. config NFSD_V4
  63. bool "NFS server support for NFS version 4"
  64. depends on NFSD && PROC_FS
  65. select FS_POSIX_ACL
  66. select RPCSEC_GSS_KRB5
  67. select CRYPTO
  68. select CRYPTO_MD5
  69. select CRYPTO_SHA256
  70. select GRACE_PERIOD
  71. select NFS_V4_2_SSC_HELPER if NFS_V4_2
  72. help
  73. This option enables support in your system's NFS server for
  74. version 4 of the NFS protocol (RFC 3530).
  75. To export files using NFSv4, you need to install additional user
  76. space programs which can be found in the Linux nfs-utils package,
  77. available from http://linux-nfs.org/.
  78. If unsure, say N.
  79. config NFSD_PNFS
  80. bool
  81. config NFSD_BLOCKLAYOUT
  82. bool "NFSv4.1 server support for pNFS block layouts"
  83. depends on NFSD_V4 && BLOCK
  84. select NFSD_PNFS
  85. select EXPORTFS_BLOCK_OPS
  86. help
  87. This option enables support for the exporting pNFS block layouts
  88. in the kernel's NFS server. The pNFS block layout enables NFS
  89. clients to directly perform I/O to block devices accessible to both
  90. the server and the clients. See RFC 5663 for more details.
  91. If unsure, say N.
  92. config NFSD_SCSILAYOUT
  93. bool "NFSv4.1 server support for pNFS SCSI layouts"
  94. depends on NFSD_V4 && BLOCK
  95. select NFSD_PNFS
  96. select EXPORTFS_BLOCK_OPS
  97. help
  98. This option enables support for the exporting pNFS SCSI layouts
  99. in the kernel's NFS server. The pNFS SCSI layout enables NFS
  100. clients to directly perform I/O to SCSI devices accessible to both
  101. the server and the clients. See draft-ietf-nfsv4-scsi-layout for
  102. more details.
  103. If unsure, say N.
  104. config NFSD_FLEXFILELAYOUT
  105. bool "NFSv4.1 server support for pNFS Flex File layouts"
  106. depends on NFSD_V4
  107. select NFSD_PNFS
  108. help
  109. This option enables support for the exporting pNFS Flex File
  110. layouts in the kernel's NFS server. The pNFS Flex File layout
  111. enables NFS clients to directly perform I/O to NFSv3 devices
  112. accessible to both the server and the clients. See
  113. draft-ietf-nfsv4-flex-files for more details.
  114. Warning, this server implements the bare minimum functionality
  115. to be a flex file server - it is for testing the client,
  116. not for use in production.
  117. If unsure, say N.
  118. config NFSD_V4_2_INTER_SSC
  119. bool "NFSv4.2 inter server to server COPY"
  120. depends on NFSD_V4 && NFS_V4_2
  121. help
  122. This option enables support for NFSv4.2 inter server to
  123. server copy where the destination server calls the NFSv4.2
  124. client to read the data to copy from the source server.
  125. If unsure, say N.
  126. config NFSD_V4_SECURITY_LABEL
  127. bool "Provide Security Label support for NFSv4 server"
  128. depends on NFSD_V4 && SECURITY
  129. help
  130. Say Y here if you want enable fine-grained security label attribute
  131. support for NFS version 4. Security labels allow security modules like
  132. SELinux and Smack to label files to facilitate enforcement of their policies.
  133. Without this an NFSv4 mount will have the same label on each file.
  134. If you do not wish to enable fine-grained security labels SELinux or
  135. Smack policies on NFSv4 files, say N.
  136. config NFSD_LEGACY_CLIENT_TRACKING
  137. bool "Support legacy NFSv4 client tracking methods (DEPRECATED)"
  138. depends on NFSD_V4
  139. default y
  140. help
  141. The NFSv4 server needs to store a small amount of information on
  142. stable storage in order to handle state recovery after reboot. Most
  143. modern deployments upcall to a userland daemon for this (nfsdcld),
  144. but older NFS servers may store information directly in a
  145. recoverydir, or spawn a process directly using a usermodehelper
  146. upcall.
  147. These legacy client tracking methods have proven to be probelmatic
  148. and will be removed in the future. Say Y here if you need support
  149. for them in the interim.