Home
last modified time | relevance | path

Searched refs:last_unlink_trans (Results 1 - 6 of 6) sorted by relevance

/kernel/linux/linux-5.10/fs/btrfs/
H A Dbtrfs_inode.h172 u64 last_unlink_trans; member
H A Dtree-log.c5521 * its last_unlink_trans value - this is safe because any task setting
5522 * last_unlink_trans must take the log_mutex and it must do this before it does
5524 * sets last_unlink_trans it means we've logged a consistent version/state of
5526 * commit (the concurrent task might have only updated last_unlink_trans before
5536 if (inode->last_unlink_trans > fs_info->last_trans_committed) { in btrfs_must_commit_transaction()
5567 * we can use the last_unlink_trans field to record renames in check_parent_dirs_for_sync()
5572 inode->last_unlink_trans <= last_committed) in check_parent_dirs_for_sync()
6162 * we can use the last_unlink_trans field to record renames in btrfs_log_inode_parent()
6167 inode->last_unlink_trans <= last_committed) { in btrfs_log_inode_parent()
6216 if (inode->last_unlink_trans > last_committe in btrfs_log_inode_parent()
[all...]
H A Dinode.c3375 * have been evicted, and therefore the exact value of last_unlink_trans in btrfs_read_locked_inode()
3394 * Setting last_unlink_trans to last_trans is a pessimistic approach, in btrfs_read_locked_inode()
3399 BTRFS_I(inode)->last_unlink_trans = BTRFS_I(inode)->last_trans; in btrfs_read_locked_inode()
3402 * Same logic as for last_unlink_trans. We don't persist the generation in btrfs_read_locked_inode()
4145 u64 last_unlink_trans; in btrfs_rmdir() local
4165 last_unlink_trans = BTRFS_I(inode)->last_unlink_trans; in btrfs_rmdir()
4174 * Propagate the last_unlink_trans value of the deleted dir to in btrfs_rmdir()
4184 if (last_unlink_trans >= trans->transid) in btrfs_rmdir()
4185 BTRFS_I(dir)->last_unlink_trans in btrfs_rmdir()
[all...]
/kernel/linux/linux-6.6/fs/btrfs/
H A Dbtrfs_inode.h202 u64 last_unlink_trans; member
H A Dtree-log.c5603 * cases (last_unlink_trans will match the current transaction); in add_conflicting_inode()
5609 * case it has a last_unlink_trans == trans->transid, due to moving in add_conflicting_inode()
6447 if (full_dir_logging && inode->last_unlink_trans >= trans->transid) { in btrfs_log_inode()
7020 * we can use the last_unlink_trans field to record renames in btrfs_log_inode_parent()
7025 inode->last_unlink_trans < trans->transid) { in btrfs_log_inode_parent()
7074 if (inode->last_unlink_trans >= trans->transid) { in btrfs_log_inode_parent()
7318 * So, we use the last_unlink_trans field to put this transid in btrfs_record_unlink_dir()
7323 inode->last_unlink_trans = trans->transid; in btrfs_record_unlink_dir()
7355 dir->last_unlink_trans = trans->transid; in btrfs_record_unlink_dir()
7375 dir->last_unlink_trans in btrfs_record_snapshot_destroy()
[all...]
H A Dinode.c3817 * have been evicted, and therefore the exact value of last_unlink_trans in btrfs_read_locked_inode()
3836 * Setting last_unlink_trans to last_trans is a pessimistic approach, in btrfs_read_locked_inode()
3841 BTRFS_I(inode)->last_unlink_trans = BTRFS_I(inode)->last_trans; in btrfs_read_locked_inode()
3844 * Same logic as for last_unlink_trans. We don't persist the generation in btrfs_read_locked_inode()
4597 u64 last_unlink_trans; in btrfs_rmdir() local
4632 last_unlink_trans = BTRFS_I(inode)->last_unlink_trans; in btrfs_rmdir()
4640 * Propagate the last_unlink_trans value of the deleted dir to in btrfs_rmdir()
4650 if (last_unlink_trans >= trans->transid) in btrfs_rmdir()
4651 BTRFS_I(dir)->last_unlink_trans in btrfs_rmdir()
[all...]

Completed in 32 milliseconds