Lines Matching full:its
23 A process wants to clone its own namespace, but still wants to access the CD
131 This is the mount we are familiar with. Its the default type.
163 A) A process wants to clone its own namespace, but still wants to
181 B) A process wants its mounts invisible to any other process, but
192 of its namespace as slave::
275 /mnt or /tmp reflect in all the other mounts of its peer
298 has its own peer group too. This vfsmount receives propagation
299 events from its master vfsmount, and also forwards propagation
300 events to its 'peer group' and to its slave vfsmounts.
302 Strictly speaking, the vfsmount is shared having its own
347 * if the shared mount is the only mount in its peer group, making it
354 the state of a mount depending on type of the destination mount. Its
385 which is clone of 'A', is created. Its root dentry is 'a' . 'C' is
394 which is clone of 'A', is created. Its root dentry is 'a'. 'C' is
402 mount 'C' which is clone of 'A', is created. Its root dentry is 'a' .
407 propagation tree for 'B'. And finally the mount 'C' and its peer group
416 Its root dentry is 'a'. 'C' is mounted on mount 'B' at dentry 'b'.
419 which is a clone of 'A' is created. Its root dentry is 'a'. 'C' is
424 new mount 'C' which is a clone of 'A' is created. Its root dentry is
655 its root dentry is 1. Let's call this mount 'A'
863 links together all the slaves that its master vfsmount
884 you need to go through _all_ ->mnt_slave_list of its members.
964 b) Do not attach any of the trees to its destination.
965 However note down its ->mnt_parent and ->mnt_mountpoint