Lines Matching refs:propagation

129 2c) A private mount does not forward or receive propagation.
258 A 'propagation event' is defined as event generated on a vfsmount
283 propagation events and does not forward propagation events.
299 has its own peer group too. This vfsmount receives propagation
300 events from its master vfsmount, and also forwards propagation
317 receive or forward any propagation events.
322 receive or forward any propagation events and cannot
389 propagates to. A new propagation tree containing 'C1',..,'Cn' is
390 created. This propagation tree is identical to the propagation tree of
398 propagates to. A new propagation tree is set containing all new mounts
400 propagation tree for 'B'.
406 'B' propagates to. A new propagation tree containing the new mounts
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
504 propagation from mount 'B'. A new propagation tree is created in the
505 exact same configuration as that of 'B'. This new propagation tree
507 propagation tree is appended to the already existing propagation tree
513 propagation from mount 'B'. The mount 'A' becomes a shared mount and a
514 propagation tree is created which is identical to that of
515 'B'. This new propagation tree contains all the new mounts 'A1',
521 receive propagation from mount 'B'. A new propagation tree is created
522 in the exact same configuration as that of 'B'. This new propagation
524 propagation tree is appended to the already existing propagation tree of
531 propagation from 'B'. And since the mount 'A' is unbindable, cloning
571 'b' on mounts that receive propagation from mount 'B' and does not have
860 send/receives propagation events.
872 receives propagation.
875 takes two more flags to indicate the propagation status of
890 individual lists does not affect propagation or the way propagation
896 A example propagation tree looks as shown in the figure below.
936 NOTE: The propagation tree is orthogonal to the mount tree.
967 propagation from the destination mount.
970 c) Link all the new mounts to form a propagation tree that
971 is identical to the propagation tree of the destination
975 propagation trees; where 'n' is the number of mounts in the
992 all the propagation related functionality resides in the file pnode.c