@@ -145,7 +145,8 @@ Bind mounts and OverlayFS
145145
146146Landlock enables to restrict access to file hierarchies, which means that these
147147access rights can be propagated with bind mounts (cf.
148- :doc: `/filesystems/sharedsubtree `) but not with :doc: `/filesystems/overlayfs `.
148+ Documentation/filesystems/sharedsubtree.rst) but not with
149+ Documentation/filesystems/overlayfs.rst.
149150
150151A bind mount mirrors a source file hierarchy to a destination. The destination
151152hierarchy is then composed of the exact same files, on which Landlock rules can
@@ -170,8 +171,8 @@ Inheritance
170171
171172Every new thread resulting from a :manpage: `clone(2)` inherits Landlock domain
172173restrictions from its parent. This is similar to the seccomp inheritance (cf.
173- :doc: ` /userspace-api/seccomp_filter ` ) or any other LSM dealing with task's
174- :manpage: `credentials(7)`. For instance, one process's thread may apply
174+ Documentation /userspace-api/seccomp_filter.rst ) or any other LSM dealing with
175+ task's :manpage: `credentials(7)`. For instance, one process's thread may apply
175176Landlock rules to itself, but they will not be automatically applied to other
176177sibling threads (unlike POSIX thread credential changes, cf.
177178:manpage: `nptl(7)`).
@@ -278,7 +279,7 @@ Memory usage
278279------------
279280
280281Kernel memory allocated to create rulesets is accounted and can be restricted
281- by the :doc: ` /admin-guide/cgroup-v1/memory ` .
282+ by the Documentation /admin-guide/cgroup-v1/memory.rst .
282283
283284Questions and answers
284285=====================
@@ -303,7 +304,7 @@ issues, especially when untrusted processes can manipulate them (cf.
303304Additional documentation
304305========================
305306
306- * :doc: ` /security/landlock `
307+ * Documentation /security/landlock.rst
307308* https://landlock.io
308309
309310.. Links
0 commit comments