Lines Matching defs:new
210 * becoming the new parent got renamed too, we can't rename/move the
376 result_string = "new";
1379 * number of bytes than what we found before, use the new one so that
1485 * We may have not added any roots to the new cache entry, which means
1487 * allowed to clone. Cache the new entry as it's still useful to avoid
1681 * data from the new extent location. Otherwise we will fail
2111 * Used by process_recorded_refs to determine if a new ref would overwrite an
2416 * inodes "orphan" name instead of the real name and stop. Same with new inodes
2425 * 3. When an inode is moved around or gets new links, it may overwrite the ref
2428 * process this overwritten inode, it is restored at a new place by moving
3057 struct recorded_ref *new;
3059 new = recorded_ref_alloc();
3060 if (!new)
3063 new->dir = ref->dir;
3064 new->dir_gen = ref->dir_gen;
3065 list_add_tail(&new->list, list);
3628 * After rename/move, need to update the utimes of both new parent(s)
4069 * we use here a new path.
4093 * When processing the new references for an inode we may orphanize an existing
4094 * directory inode because its old name conflicts with one of the new references
4095 * of the current inode. Later, when processing another new reference of our
4120 * collecting all its new references we set a full path of "d1/d2" for its new
4121 * reference with name "d2". When we start processing the new references we
4122 * start by processing the new reference with name "d1", and this results in
4124 * move on the next new reference, with name "d2", and we find out we must
4127 * new reference, which is "d1/d2" and not "o259-6-0/d2" - this makes the
4129 * to "o259-6-0/" when processing the previous new reference. So in this case we
4130 * must recompute the path in the new reference and use it for the new
4227 * new references to orphanize any unprocessed inodes that may have a
4228 * reference that conflicts with one of the new references of the current
4229 * inode. This needs to happen first because a new reference may conflict
4254 * Processing the new reference for inode 257 with name "b" may happen
4255 * before processing the new reference with name "testdir". If so, we
4271 * Check if this new ref would overwrite the first ref of another
4351 * collided with a new reference that we already
4432 * link/move the ref to the new place. If we have an orphan
4448 * dirs, we always have one new and one deleted
4555 * of this inode and no new refs were added for the current
6955 * means that the original inode was deleted and new inode
6957 * deleted and the new one as new.
6978 * Now process the inode as if it was new.
7009 * inode as if they were all new.
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
7042 * refs of the right tree as deleted and all refs of the left tree as new.
7068 * Process new/deleted/changed xattrs. We skip processing in the
7095 * Process new/deleted/changed extents. We skip processing in the
7110 * get modified or replaced with a new one). Note that deduplication
7564 * restart the start from the current commit roots and clone the new leaves so
7566 * make us clone the wrong data in case there are new extents using the old
7643 * every changed/new/deleted item it finds.
7706 * If left < right treat left item as new, advance left tree
7764 * root. We know that all new nodes/leaves in the left root must have