Lines Matching defs:refs
1514 const u64 refs = btrfs_extent_refs(leaf, ei);
1531 if (refs == 1 && sctx->clone_roots_cnt == 1)
1542 if (refs > SEND_MAX_EXTENT_REFS)
2179 * process_recorded_refs also uses it to avoid unlinking of refs that were
2417 * that were not created yet and overwritten inodes/refs.
2420 * 1. When an inode is freshly created and thus no valid refs are available yet
2421 * 2. When a directory lost all it's refs (deleted) but still has dir items
2832 * a valid path yet because we did not process the refs yet. So, the inode
4370 * We may have refs where the parent directory does not exist
4374 * did already happen before due to other refs in the same dir.
4382 * First check if any of the current inodes refs did
4521 * We have a non dir inode. Go through all deleted refs and
4555 * of this inode and no new refs were added for the current
4575 * In case we had refs into dirs that were not processed yet,
4651 static int record_ref_in_tree(struct rb_root *root, struct list_head *refs,
4681 list_add_tail(&ref->list, refs);
4801 * Record and process all refs at once. Needed when an inode changes the
6643 * We have processed the refs and thus need to advance send_progress.
6644 * Now, calls to get_cur_xxx will take the updated refs of the current
6846 * functions that the current inode's refs are not updated yet. Later,
7035 * We have to process new refs before deleted refs, but compare_trees gives us
7036 * the new and deleted refs mixed. To fix this, we record the new/deleted refs
7039 * changed_inode did already initiate processing of refs. The reason for this is
7040 * that in this case, compare_tree actually compares the refs of 2 different
7042 * refs of the right tree as deleted and all refs of the left tree as new.