Home
last modified time | relevance | path

Searched refs:last_unlink_trans (Results 1 – 3 of 3) sorted by relevance

/linux/fs/btrfs/
H A Dbtrfs_inode.h302 u64 last_unlink_trans; member
H A Dtree-log.c2486 * parent inodes when inode->last_unlink_trans is in replay_one_buffer()
5718 * cases (last_unlink_trans will match the current transaction); in add_conflicting_inode()
5724 * case it has a last_unlink_trans == trans->transid, due to moving in add_conflicting_inode()
6558 if (full_dir_logging && inode->last_unlink_trans >= trans->transid) { in btrfs_log_inode()
7134 * we can use the last_unlink_trans field to record renames in btrfs_log_inode_parent()
7139 inode->last_unlink_trans < trans->transid) { in btrfs_log_inode_parent()
7191 if (inode->last_unlink_trans >= trans->transid) { in btrfs_log_inode_parent()
7441 * So, we use the last_unlink_trans field to put this transid in btrfs_record_unlink_dir()
7446 inode->last_unlink_trans = trans->transid; in btrfs_record_unlink_dir()
7478 dir->last_unlink_trans in btrfs_record_unlink_dir()
[all...]
H A Dinode.c3971 * have been evicted, and therefore the exact value of last_unlink_trans in btrfs_read_locked_inode()
3990 * Setting last_unlink_trans to last_trans is a pessimistic approach, in btrfs_read_locked_inode()
3995 inode->last_unlink_trans = inode->last_trans; in btrfs_read_locked_inode()
3998 * Same logic as for last_unlink_trans. We don't persist the generation in btrfs_read_locked_inode()
4732 * Propagate the last_unlink_trans value of the deleted dir to its in btrfs_rmdir()
4745 if (inode->last_unlink_trans >= trans->transid) in btrfs_rmdir()
7836 ei->last_unlink_trans = 0; in btrfs_alloc_inode()