Lines Matching full:remove
85 * Below is a state machine diagram for attr remove operations. The XFS_DAS_*
96 * have attr to remove? ──n──> done
126 * Have remote blks to remove? ───y─────┐
127 * │ ^ remove the blks
133 * │ remove │
143 * remove leaf and
329 * │ need to remove │
335 * │ remove │
342 * │ remove? │
350 * │ remove leaf │
400 * remove blks? ─n──┤
405 * remove │
412 * remove │
442 * ADD and REMOVE states for a specific format to be sequential so
447 XFS_DAS_SF_REMOVE, /* Initial sf replace/remove state */
450 XFS_DAS_LEAF_REMOVE, /* Initial leaf replace/remove state */
453 XFS_DAS_NODE_REMOVE, /* Initial node replace/remove state */
455 /* Leaf state set/replace/remove sequence */
461 XFS_DAS_LEAF_REMOVE_ATTR, /* Remove the old attr from a leaf */
469 XFS_DAS_NODE_REMOVE_ATTR, /* Remove the old attr from a node */
555 XFS_ATTRUPDATE_REMOVE, /* remove attr */
587 * When called from the completion of a attr remove to determine the in xfs_attr_init_add_state()
589 * on a pure remove, but we grab the next state before we check if a in xfs_attr_init_add_state()
592 * null, we were called from a pure remove operation and so we are done. in xfs_attr_init_add_state()
619 * value, so even when we remove the attr first we still have the information in