Lines Matching defs:new
687 * @start: The new start
688 * @end: The new end
736 * the kernel to generate new VMAs when old one could be
1072 * the same as 'old', the other will be the new one that is trying
1105 * to allocate a new anon_vma. It checks because a repetitive
1755 * This mmap-allocator allocates new areas top-down from below the
2243 * that can grow up. Only sequentially, though, so the new address must
2370 struct vm_area_struct *new;
2382 new = vm_area_dup(vma);
2383 if (!new)
2387 new->vm_end = addr;
2389 new->vm_start = addr;
2390 new->vm_pgoff += ((addr - vma->vm_start) >> PAGE_SHIFT);
2394 vma_iter_config(vmi, new->vm_start, new->vm_end);
2395 if (vma_iter_prealloc(vmi, new))
2398 err = vma_dup_policy(vma, new);
2402 err = anon_vma_clone(new, vma);
2406 if (new->vm_file)
2407 get_file(new->vm_file);
2409 if (new->vm_ops && new->vm_ops->open)
2410 new->vm_ops->open(new);
2413 vma_start_write(new);
2416 vp.insert = new;
2422 vma->vm_pgoff += (addr - new->vm_start) >> PAGE_SHIFT;
2427 /* vma_complete stores the new vma */
2436 mpol_put(vma_policy(new));
2440 vm_area_free(new);
2445 * Split a vma into two pieces at address 'addr', a new vma is allocated
2908 * then new mapped in-place (which must be aimed as
2909 * a completely new data area).
3091 * do not match then create a new anonymous VMA. Eventually we may be able to
3116 * occur after forking, so the expand will only happen on new VMAs.
3334 * Copy the vma structure to a new location in the same mm,
3349 * If anonymous vma has not yet been faulted, update new pgoff
3350 * to match new location, to increase its chance of merging.
3595 * Insert a new vma covering the given region, with the given flags.
3676 * altering the vma layout. It's also needed in write mode to avoid new