Lines Matching defs:new
130 * becoming the new parent got renamed too, we can't rename/move the
290 result_string = "new";
1837 * Used by process_recorded_refs to determine if a new ref would overwrite an
2262 * inodes "orphan" name instead of the real name and stop. Same with new inodes
2271 * 3. When an inode is moved around or gets new links, it may overwrite the ref
2274 * process this overwritten inode, it is restored at a new place by moving
2782 * We need to process new refs before deleted refs, but compare_tree gives us
2804 struct recorded_ref *new;
2806 new = kmalloc(sizeof(*ref), GFP_KERNEL);
2807 if (!new)
2810 new->dir = ref->dir;
2811 new->dir_gen = ref->dir_gen;
2812 new->full_path = NULL;
2813 INIT_LIST_HEAD(&new->list);
2814 list_add_tail(&new->list, list);
3339 * After rename/move, need to update the utimes of both new parent(s)
3798 * we use here a new path.
3822 * When processing the new references for an inode we may orphanize an existing
3823 * directory inode because its old name conflicts with one of the new references
3824 * of the current inode. Later, when processing another new reference of our
3849 * collecting all its new references we set a full path of "d1/d2" for its new
3850 * reference with name "d2". When we start processing the new references we
3851 * start by processing the new reference with name "d1", and this results in
3853 * move on the next new reference, with name "d2", and we find out we must
3856 * new reference, which is "d1/d2" and not "o259-6-0/d2" - this makes the
3858 * to "o259-6-0/" when processing the previous new reference. So in this case we
3859 * must recompute the path in the new reference and use it for the new
3957 * new references to orphanize any unprocessed inodes that may have a
3958 * reference that conflicts with one of the new references of the current
3959 * inode. This needs to happen first because a new reference may conflict
3984 * Processing the new reference for inode 257 with name "b" may happen
3985 * before processing the new reference with name "testdir". If so, we
4001 * Check if this new ref would overwrite the first ref of another
4085 * collided with a new reference that we already
4165 * link/move the ref to the new place. If we have an orphan
4181 * dirs, we always have one new and one deleted
4289 * of this inode and no new refs were added for the current
6374 * items completely if it's a new inode, or if it's a changed inode
6415 * means that the original inode was deleted and new inode
6417 * deleted and the new one as new.
6436 * Now process the inode as if it was new.
6462 * they were all new.
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
6494 * refs of the right tree as deleted and all refs of the left tree as new.
6520 * Process new/deleted/changed xattrs. We skip processing in the
6547 * Process new/deleted/changed extents. We skip processing in the
6562 * get modified or replaced with a new one). Note that deduplication
6843 * every changed/new/deleted item it finds.
6905 * If left < right treat left item as new, advance left tree