Lines Matching full:remove

84  * Below is a state machine diagram for attr remove operations. The  XFS_DAS_*
95  *        have attr to remove? ──n──> done
125  *   Have remote blks to remove? ───y─────┐
126  *              │        ^          remove the blks
132  *              │      remove             │
142  *       remove leaf and
328  *   │          need to remove    │
334  *   │               remove       │
341  *   │              remove?       │
349  *   │            remove leaf     │
399  *               remove blks? ─n──┤
404  *                   remove       │
411  *                   remove       │
441 	 * ADD and REMOVE states for a specific format to be sequential so
446 	XFS_DAS_SF_REMOVE,		/* Initial sf replace/remove state */
449 	XFS_DAS_LEAF_REMOVE,		/* Initial leaf replace/remove state */
452 	XFS_DAS_NODE_REMOVE,		/* Initial node replace/remove state */
454 	/* Leaf state set/replace/remove sequence */
460 	XFS_DAS_LEAF_REMOVE_ATTR,	/* Remove the old attr from a leaf */
468 	XFS_DAS_NODE_REMOVE_ATTR,	/* Remove the old attr from a node */
574 	 * When called from the completion of a attr remove to determine the  in xfs_attr_init_add_state()
576 	 * on a pure remove, but we grab the next state before we check if a  in xfs_attr_init_add_state()
579 	 * null, we were called from a pure remove operation and so we are done.  in xfs_attr_init_add_state()
607  * value, so even when we remove the attr first we still have the information in