Lines Matching defs:transaction
20 * transaction's revoked blocks to the journal
22 * + Recovery: during recovery we record the transaction ID of all
29 * single transaction:
33 * cancel the revoke before the transaction commits.
40 * in the current transaction, so any revoke for that block in the
41 * transaction must have happened after the block was journaled and so
73 journal replay, this involves recording the transaction ID of the
74 last transaction to revoke this block. */
303 * crash after this current transaction commits. Any subsequent
304 * metadata writes of the buffer in this transaction cancel the
409 * discarded, and then reallocated within the same transaction. In such
473 /* hfsplus_jbd_switch_revoke table select j_revoke for next transaction
498 hfsplus_transaction_t *transaction)
510 /* select revoke table for committing transaction */
520 write_one_revoke_record(journal, transaction,
539 hfsplus_transaction_t *transaction,
574 header->h_sequence = cpu_to_be32(transaction->t_tid);
578 hfsplus_jbd_file_buffer(descriptor, transaction, HFSPLUS_BJ_LogCtl);
626 * check whether a given block in a given transaction should be replayed
628 * transaction)
659 * that block been revoked? A revoke record with a given transaction
660 * sequence number revokes all blocks in that transaction and earlier