mremap-check-if-its-possible-to-split-original-vma.patch removed from -mm tree
The patch titled
Subject: mremap: check if it's possible to split original vma
has been removed from the -mm tree. Its filename was
mremap-check-if-its-possible-to-split-original-vma.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Dmitry Safonov <[email protected]>
Subject: mremap: check if it's possible to split original vma
If original VMA can't be split at the desired address, do_munmap() will fail and leave both new-copied VMA and old VMA. De-facto it's MREMAP_DONTUNMAP behaviour, which is unexpected.
Currently, it may fail such way for hugetlbfs and dax device mappings.
Minimize such unpleasant situations to OOM by checking .may_split() before attempting to create a VMA copy.
---
mm/mremap.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
mm/mremap.c renamed from mm/mremap.c~mremap-check-if-its-possible-to-split-original-vma +10 -1
@@ -493,7 +493,7 @@ static unsigned long move_vma(struct vm_unsigned long excess =0 ;unsigned long hiwater_vm;int split =0 ; -int err; +int err =0 ;bool need_rmap_locks;/*
@@ -503,6 +503,15 @@ static unsigned long move_vma(struct vm_if (mm->map_count >= sysctl_max_map_count -3 )return -ENOMEM ; +if (vma->vm_ops && vma->vm_ops->may_split) { +if (vma->vm_start != old_addr) + err = vma->vm_ops->may_split (vma, old_addr); +if (!err && vma->vm_end != old_addr + old_len) + err = vma->vm_ops->may_split (vma, old_addr + old_len); +if (err) +return err; + } +/* * Advise KSM to break any KSM pages in the area to be moved: * it would be confusing if they were to turn up at the new
_
Patches currently in -mm which might be from [email protected] are