Lines Matching full:hierarchy

39     For these rules, the object is a file hierarchy,
146 file hierarchy ``/usr``.  Without another rule, write actions would then be
230 It is recommended to set access rights to file hierarchy leaves as much as
232 read-only hierarchy and ``~/tmp/`` as a read-write hierarchy, compared to
233 ``~/`` as a read-only hierarchy and ``~/tmp/`` as a read-write hierarchy.
272 A bind mount mirrors a source file hierarchy to a destination.  The destination
273 hierarchy is then composed of the exact same files, on which Landlock rules can
281 the mount point.  This merge hierarchy may include files from the upper and
282 lower layers, but modifications performed on the merge hierarchy only reflect
286 OverlayFS layer will not restrict the resulted merged hierarchy, and vice versa.
533 guarantees that they need through the file hierarchy, by only allowing the
546 from a parent to its hierarchy.  Because files are identified and restricted by
547 their hierarchy, moving or linking a file from one directory to another implies
548 propagation of the hierarchy constraints, or restriction of these actions