hesela.devMount propagation
Mount propagation controls whether mount and unmount events are replicated between related Linux mounts.
Shared mounts exchange events within a peer group. A slave receives events from its master peer group without sending them back upstream; it may also be shared with its own peer group. Private mounts neither send nor receive propagated events. An unbindable mount blocks propagation in both directions and cannot be bind-mounted. [1]
Propagation concerns events immediately beneath each mount, not replication of file contents. Descendant mounts have their own settings; changing one mount to private does not recursively privatize them. Namespace cloning can retain shared relationships, so a separate namespace is not by itself an event-isolation guarantee. [2]
/proc/PID/mountinfo exposes optional shared and master tags; both can occur for a shared-and-slave mount. A private mount has none of the recognized propagation tags. These fields describe topology, separately from per-mount and superblock access flags. [3] A private tree does not freeze data reachable through another writable attachment. [1] [4]
Relations
- related
- Mount namespace, Bind mount, Read-only mount
Citations
- Linux man-pages: mount_namespaces(7), immediate event scope and namespace copies
- Linux man-pages: proc_pid_mountinfo(5), propagation tags and option layers
- util-linux v2.41.1: mount(8), bind mounts and read-only setting notes
Sources & caveats
- Documentation synthesis from primary Linux sources checked on the access date; no privileged mounting, namespace experiment or device-write measurement was performed.
- The file-content boundary combines the topology rules with the documented semantics of writable bind attachments; it is an interpretive synthesis, not a device observation.