52  * Initialize the precomputed transaction reservation values
64  * Free the transaction structure.  If there is more clean up
83  * This is called to create a new transaction which will share the
84  * permanent log reservation of the given transaction.  The remaining
86  * implies that the original transaction is no longer allowed to allocate
88  * be added to the new transaction explicitly.
101 	 * Initialize the new transaction structure.  in xfs_trans_dup()
116 	/* We gave our writer reference to the new transaction */  in xfs_trans_dup()
138  * given transaction.  This must be done before allocating any resources
139  * within the transaction.
174 	 * Reserve the log space needed for this transaction.  in xfs_trans_reserve()
289 		 * We weren't able to reserve enough space for the transaction.  in xfs_trans_alloc()
312  * Create an empty transaction with no reservation.  This is a defensive
316  * grabbed as part of a transaction can be re-grabbed.  The verifiers will
320  * Note the zero-length reservation; this transaction MUST be cancelled without
339  * to the file system's superblock when the transaction commits.
340  * For now, just store the change in the transaction structure.
342  * Mark the transaction structure to indicate that the superblock
347  * superblock dirty in this transaction if we modify these fields.
348  * We still need to update the transaction deltas so that they get
351  * only fields in the superblock that the transaction modifies.
375 		 * Track the number of blocks allocated in the transaction.  in xfs_trans_mod_sb()
390 			 * reservation across chains of transaction rolls that  in xfs_trans_mod_sb()
415 		 * transaction.  Make sure it does not exceed the  in xfs_trans_mod_sb()
476  * to bring the superblock buffer into the current transaction
609  * XFS_TRANS_SB_DIRTY will not be set when the transaction is updated but we
632 	 *  - positive values indicate blocks freed in the transaction.  in xfs_trans_unreserve_and_mod_sb()
633 	 *  - negative values indicate blocks allocated in the transaction  in xfs_trans_unreserve_and_mod_sb()
635 	 * Negative values can only happen if the transaction has a block  in xfs_trans_unreserve_and_mod_sb()
705 /* Add the given log item to the transaction's list of log items. */
721  * Unlink the log item from the transaction. the log item is no longer
722  * considered dirty in this transaction, as the linked transaction has
733 /* Detach and unlock all of the items in a transaction */
753  * Sort transaction items prior to running precommit operations. This will
795  * Run transaction precommit functions.
798  * trigger a shutdown to abort the transaction. There is no recovery possible
799  * from errors at this point as the transaction is dirty....
817 	 * Precommit operations can remove the log item from the transaction  in xfs_trans_run_precommits()
837  * Commit the given transaction to the log.
840  * transaction abort mechanism. Logically after the filesystem
844  * caller may assume that all locked objects joined to the transaction
846  * Do not reference the transaction structure after this call.
862 	 * Commit per-transaction changes that are not already tracked through  in __xfs_trans_commit()
863 	 * log items.  This can add dirty log items to the transaction.  in __xfs_trans_commit()
874 	 * If there is nothing to be logged by the transaction,  in __xfs_trans_commit()
876 	 * transaction and free the transaction structure.  in __xfs_trans_commit()
901 	 * If the transaction needs to be synchronous, then force the  in __xfs_trans_commit()
917 	 * It is indeed possible for the transaction to be not dirty but  in __xfs_trans_commit()
958  * Unlock all of the transaction's items and free the transaction.  If the
959  * transaction is dirty, we must shut down the filesystem because there is no
962  * If the transaction has made a log reservation, make sure to release it as
966  * be called after the transaction has effectively been aborted due to the mount
968  * transaction is dirty we will shut the mount down and, in doing so, that
984 	 * It's never valid to cancel a transaction with deferred ops attached,  in xfs_trans_cancel()
985 	 * because the transaction is effectively dirty.  Complain about this  in xfs_trans_cancel()
1031  * chunk we've been working on and get a new transaction to continue.
1052 	 * Commit the current transaction.  in xfs_trans_roll()
1056 	 * the duplicate transaction that gets returned.  in xfs_trans_roll()
1063 	 * Reserve space in the log for the next transaction.  in xfs_trans_roll()
1075  * Allocate an transaction, lock and join the inode to it, and reserve quota.
1079  * releasing ILOCK_EXCL if a new transaction is returned.
1133  * Try to reserve more blocks for a transaction.
1135  * This is for callers that need to attach resources to a transaction, scan
1138  * fail due to ENOSPC, so the caller must be able to cancel the transaction
1153  * Try to reserve more blocks and file quota for a transaction.  Same
1195  * Allocate an transaction in preparation for inode creation by reserving quota
1234  * Allocate an transaction, lock and join the inode to it, and reserve quota
1240  * transaction is committed or cancelled.
1348  * Allocate an transaction, lock and join the directory and child inodes to it,
1356  * transaction is committed or cancelled.