fs/xfs/xfs_rmap_item.c

49  * Freeing the RUI requires that we remove it from the AIL if it has already
50  * been placed there. However, the RUI may not yet have been placed in the AIL
53  * count to ensure only the last caller frees the RUI.
81  * given rui log item. We use only 1 iovec, and we point that
82  * at the rui_log_format structure embedded in the rui item.
84  * slots in the rui item have been filled.
105  * The unpin operation is the last place an RUI is manipulated in the log. It is
107  * either case, the RUI transaction has been successfully committed to make it
108  * this far. Therefore, we expect whoever committed the RUI to either construct
110  * drop the log's RUI reference now that the log is done with it.
123  * The RUI has been either committed or aborted if the transaction has been
125  * constructed and thus we free the RUI here directly.
135  * Allocate and initialize an rui item with the given number of extents.
201  * the transaction is cancelled, drop our reference to the RUI and free the
346 /* Add this deferred RUI to the transaction. */
413 /* Is this recovered RUI ok? */
521 	 * RUI.  If any are bad, then assume that all are bad and  in xfs_rmap_recover_work()
522 	 * just toss the RUI.  in xfs_rmap_recover_work()
624  * item from the rui format structure which was logged on disk.
625  * It allocates an in-core rui, copies the extents from the format
626  * structure into it, and adds the rui to the AIL with the given
672  * transaction in the log. Its purpose is to cancel the corresponding RUI if it
673  * was still in the log. To do this it searches the AIL for the RUI with an id
675  * reference, which removes the RUI from the AIL and frees it.