Kconfig 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124
  1. config OVERLAY_FS
  2. tristate "Overlay filesystem support"
  3. select EXPORTFS
  4. help
  5. An overlay filesystem combines two filesystems - an 'upper' filesystem
  6. and a 'lower' filesystem. When a name exists in both filesystems, the
  7. object in the 'upper' filesystem is visible while the object in the
  8. 'lower' filesystem is either hidden or, in the case of directories,
  9. merged with the 'upper' object.
  10. For more information see Documentation/filesystems/overlayfs.txt
  11. config OVERLAY_FS_REDIRECT_DIR
  12. bool "Overlayfs: turn on redirect directory feature by default"
  13. depends on OVERLAY_FS
  14. help
  15. If this config option is enabled then overlay filesystems will use
  16. redirects when renaming directories by default. In this case it is
  17. still possible to turn off redirects globally with the
  18. "redirect_dir=off" module option or on a filesystem instance basis
  19. with the "redirect_dir=off" mount option.
  20. Note, that redirects are not backward compatible. That is, mounting
  21. an overlay which has redirects on a kernel that doesn't support this
  22. feature will have unexpected results.
  23. If unsure, say N.
  24. config OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW
  25. bool "Overlayfs: follow redirects even if redirects are turned off"
  26. default y
  27. depends on OVERLAY_FS
  28. help
  29. Disable this to get a possibly more secure configuration, but that
  30. might not be backward compatible with previous kernels.
  31. If backward compatibility is not an issue, then it is safe and
  32. recommended to say N here.
  33. For more information, see Documentation/filesystems/overlayfs.txt
  34. If unsure, say Y.
  35. config OVERLAY_FS_INDEX
  36. bool "Overlayfs: turn on inodes index feature by default"
  37. depends on OVERLAY_FS
  38. help
  39. If this config option is enabled then overlay filesystems will use
  40. the index directory to map lower inodes to upper inodes by default.
  41. In this case it is still possible to turn off index globally with the
  42. "index=off" module option or on a filesystem instance basis with the
  43. "index=off" mount option.
  44. The inodes index feature prevents breaking of lower hardlinks on copy
  45. up.
  46. Note, that the inodes index feature is not backward compatible.
  47. That is, mounting an overlay which has an inodes index on a kernel
  48. that doesn't support this feature will have unexpected results.
  49. If unsure, say N.
  50. config OVERLAY_FS_NFS_EXPORT
  51. bool "Overlayfs: turn on NFS export feature by default"
  52. depends on OVERLAY_FS
  53. depends on OVERLAY_FS_INDEX
  54. depends on !OVERLAY_FS_METACOPY
  55. help
  56. If this config option is enabled then overlay filesystems will use
  57. the index directory to decode overlay NFS file handles by default.
  58. In this case, it is still possible to turn off NFS export support
  59. globally with the "nfs_export=off" module option or on a filesystem
  60. instance basis with the "nfs_export=off" mount option.
  61. The NFS export feature creates an index on copy up of every file and
  62. directory. This full index is used to detect overlay filesystems
  63. inconsistencies on lookup, like redirect from multiple upper dirs to
  64. the same lower dir. The full index may incur some overhead on mount
  65. time, especially when verifying that directory file handles are not
  66. stale.
  67. Note, that the NFS export feature is not backward compatible.
  68. That is, mounting an overlay which has a full index on a kernel
  69. that doesn't support this feature will have unexpected results.
  70. Most users should say N here and enable this feature on a case-by-
  71. case basis with the "nfs_export=on" mount option.
  72. Say N unless you fully understand the consequences.
  73. config OVERLAY_FS_XINO_AUTO
  74. bool "Overlayfs: auto enable inode number mapping"
  75. default n
  76. depends on OVERLAY_FS
  77. help
  78. If this config option is enabled then overlay filesystems will use
  79. unused high bits in undelying filesystem inode numbers to map all
  80. inodes to a unified address space. The mapped 64bit inode numbers
  81. might not be compatible with applications that expect 32bit inodes.
  82. If compatibility with applications that expect 32bit inodes is not an
  83. issue, then it is safe and recommended to say Y here.
  84. For more information, see Documentation/filesystems/overlayfs.txt
  85. If unsure, say N.
  86. config OVERLAY_FS_METACOPY
  87. bool "Overlayfs: turn on metadata only copy up feature by default"
  88. depends on OVERLAY_FS
  89. select OVERLAY_FS_REDIRECT_DIR
  90. help
  91. If this config option is enabled then overlay filesystems will
  92. copy up only metadata where appropriate and data copy up will
  93. happen when a file is opened for WRITE operation. It is still
  94. possible to turn off this feature globally with the "metacopy=off"
  95. module option or on a filesystem instance basis with the
  96. "metacopy=off" mount option.
  97. Note, that this feature is not backward compatible. That is,
  98. mounting an overlay which has metacopy only inodes on a kernel
  99. that doesn't support this feature will have unexpected results.
  100. If unsure, say N.