Lines Matching +full:5 +full:c
12 5) Detailed semantics
38 c. private mount
65 a b c
68 a b c
129 2c) A private mount does not forward or receive propagation.
206 C) Per-user namespace
234 A user can request v3 version of the file /usr/fs/namespace.c
235 by accessing /view/v3/usr/fs/namespace.c . The underlying
240 5) Detailed semantics
248 5a) Mount states
256 5) unbindable
319 (5) Unbindable mount
356 explained in section 5d.
358 5b) Bind semantics
385 1. 'A' is a shared mount and 'B' is a shared mount. A new mount 'C'
386 which is clone of 'A', is created. Its root dentry is 'a' . 'C' is
391 'B'. And finally the peer-group of 'C' is merged with the peer group
394 2. 'A' is a private mount and 'B' is a shared mount. A new mount 'C'
395 which is clone of 'A', is created. Its root dentry is 'a'. 'C' is
399 'C', 'C1', .., 'Cn' with exactly the same configuration as the
403 mount 'C' which is clone of 'A', is created. Its root dentry is 'a' .
404 'C' is mounted on mount 'B' at dentry 'b'. Also new mounts 'C1', 'C2',
407 'C','C1',.. 'Cn' is created. This propagation tree is identical to the
408 propagation tree for 'B'. And finally the mount 'C' and its peer group
409 is made the slave of mount 'Z'. In other words, mount 'C' is in the
415 5. 'A' is a private mount and 'B' is a non-shared(private or slave or
416 unbindable) mount. A new mount 'C' which is clone of 'A', is created.
417 Its root dentry is 'a'. 'C' is mounted on mount 'B' at dentry 'b'.
419 6. 'A' is a shared mount and 'B' is a non-shared mount. A new mount 'C'
420 which is a clone of 'A' is created. Its root dentry is 'a'. 'C' is
421 mounted on mount 'B' at dentry 'b'. 'C' is made a member of the
425 new mount 'C' which is a clone of 'A' is created. Its root dentry is
426 'a'. 'C' is mounted on mount 'B' at dentry 'b'. Also 'C' is set as a
427 slave mount of 'Z'. In other words 'A' and 'C' are both slave mounts of
428 'Z'. All mount/unmount events on 'Z' propagates to 'A' and 'C'. But
430 mount/unmount on 'C' do not propagate anywhere else.
435 5c) Rbind semantics
451 B C
455 Let's say all the mount except the mount C in the tree are
466 B' Note how the tree under C is pruned
472 5d) Move semantics
534 5. 'A' is a private mount and 'B' is a non-shared(private or slave or
549 5e) Mount semantics
562 5f) Unmount semantics
596 5g) Clone Namespace
643 C. What is the result of the following command sequence?
661 mnt. Let's call this mount 'C'
663 'B' is the slave of 'A' and 'C' is a slave of 'B'
664 A -> B -> C
672 will the mount propagate to 'B' and 'C' ?
901 A <--> B <--> C <---> D
909 In the above figure A,B,C and D all are shared and propagate to each
910 other. 'A' has got 3 slave mounts 'E' 'F' and 'G' 'C' has got 2 slave
915 A's ->mnt_share links with the ->mnt_share of 'B' 'C' and 'D'
927 C's ->mnt_slave_list links with ->mnt_slave of 'J' and 'K'
929 J and K's ->mnt_master points to struct vfsmount of C
950 8C Algorithm:
970 c) Link all the new mounts to form a propagation tree that
992 all the propagation related functionality resides in the file pnode.c