fs/xfs/xfs_rmap_item.c

47  * Freeing the RUI requires that we remove it from the AIL if it has already
48  * been placed there. However, the RUI may not yet have been placed in the AIL
51  * count to ensure only the last caller frees the RUI.
79  * given rui log item. We use only 1 iovec, and we point that
80  * at the rui_log_format structure embedded in the rui item.
82  * slots in the rui item have been filled.
103  * The unpin operation is the last place an RUI is manipulated in the log. It is
105  * either case, the RUI transaction has been successfully committed to make it
106  * this far. Therefore, we expect whoever committed the RUI to either construct
108  * drop the log's RUI reference now that the log is done with it.
121  * The RUI has been either committed or aborted if the transaction has been
123  * constructed and thus we free the RUI here directly.
133  * Allocate and initialize an rui item with the given number of extents.
198  * the transaction is cancelled, drop our reference to the RUI and free the
291  * support the RUI/RUD lifecycle rules.
308 	 * 1.) releases the RUI and frees the RUD  in xfs_trans_log_finish_rmap_update()
465 /* Is this recovered RUI ok? */
522 	 * RUI.  If any are bad, then assume that all are bad and  in xfs_rui_item_recover()
523 	 * just toss the RUI.  in xfs_rui_item_recover()
673  * item from the rui format structure which was logged on disk.
674  * It allocates an in-core rui, copies the extents from the format
675  * structure into it, and adds the rui to the AIL with the given
721  * transaction in the log. Its purpose is to cancel the corresponding RUI if it
722  * was still in the log. To do this it searches the AIL for the RUI with an id
724  * reference, which removes the RUI from the AIL and frees it.