Lines Matching defs:refs
1915 * process_recorded_refs also uses it to avoid unlinking of refs that were
2263 * that were not created yet and overwritten inodes/refs.
2266 * 1. When an inode is freshly created and thus no valid refs are available yet
2267 * 2. When a directory lost all it's refs (deleted) but still has dir items
2587 * a valid path yet because we did not process the refs yet. So, the inode
2782 * We need to process new refs before deleted refs, but compare_tree gives us
2783 * everything mixed. So we first record all refs and later process them.
4104 * We may have refs where the parent directory does not exist
4108 * did already happen before due to other refs in the same dir.
4116 * First check if any of the current inodes refs did
4255 * We have a non dir inode. Go through all deleted refs and
4289 * of this inode and no new refs were added for the current
4309 * In case we had refs into dirs that were not processed yet,
4355 void *ctx, struct list_head *refs)
4378 ret = __record_ref(refs, dir, gen, p);
4555 * Record and process all refs at once. Needed when an inode changes the
6106 * We have processed the refs and thus need to advance send_progress.
6107 * Now, calls to get_cur_xxx will take the updated refs of the current
6223 struct list_head *refs;
6233 ppctx->refs);
6259 ctx.refs = &deleted_refs;
6327 * functions that the current inode's refs are not updated yet. Later,
6487 * We have to process new refs before deleted refs, but compare_trees gives us
6488 * the new and deleted refs mixed. To fix this, we record the new/deleted refs
6491 * changed_inode did already initiate processing of refs. The reason for this is
6492 * that in this case, compare_tree actually compares the refs of 2 different
6494 * refs of the right tree as deleted and all refs of the left tree as new.