[PATCH v10 02/16] vrange: Clear volatility on new mmaps

From: Minchan Kim
Date: Thu Jan 02 2014 - 02:13:55 EST

From: John Stultz <john.stultz@xxxxxxxxxx>

At lsf-mm, the issue was brought up that there is a precedence with
interfaces like mlock, such that new mappings in a pre-existing range
do no inherit the mlock state.

This is mostly because mlock only modifies the existing vmas, and so
any new mmaps create new vmas, which won't be mlocked.

Since volatility is not stored in the vma (for good cause, specifically
as we'd have to have manage file volatility differently from anonymous
and we're likely to manage volatility on small chunks of memory, which
would cause lots of vma splitting and churn), this patch clears volitility
on new mappings, to ensure that we don't inherit volatility if memory in
an existing volatile range is unmapped and then re-mapped with something

Thus, this patch forces any volatility to be cleared on mmap.

XXX: We expect this patch to be not well loved by mm folks, and are open
to alternative methods here. Its more of a place holder to address
the issue from lsf-mm and hopefully will spur some further discussion.

Minchan does have an alternative solution[1], but I'm not a big fan of it
yet, so this simpler approach is a placeholder for now.

[1] https://git.kernel.org/cgit/linux/kernel/git/minchan/linux.git/commit/?h=vrange-working&id=821f58333b381fd88ee7f37fd9c472949756c74e

Cc: Mel Gorman <mel@xxxxxxxxx>
Cc: Hugh Dickins <hughd@xxxxxxxxxx>
Cc: Dave Hansen <dave.hansen@xxxxxxxxx>
Cc: Rik van Riel <riel@xxxxxxxxxx>
Cc: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxx>
Cc: Michel Lespinasse <walken@xxxxxxxxxx>
Cc: Johannes Weiner <hannes@xxxxxxxxxxx>
[minchan: add link alternative solution]
Signed-off-by: Minchan Kim <minchan@xxxxxxxxxx>
Signed-off-by: John Stultz <john.stultz@xxxxxxxxxx>
include/linux/vrange.h | 2 ++
mm/mmap.c | 5 +++++
mm/vrange.c | 8 ++++++++
3 files changed, 15 insertions(+)

diff --git a/include/linux/vrange.h b/include/linux/vrange.h
index 2b96ee1ee75b..ef153c8a88d1 100644
--- a/include/linux/vrange.h
+++ b/include/linux/vrange.h
@@ -36,6 +36,8 @@ static inline int vrange_type(struct vrange *vrange)
return vrange->owner->type;

+extern int vrange_clear(struct vrange_root *vroot,
+ unsigned long start, unsigned long end);
extern void vrange_root_cleanup(struct vrange_root *vroot);
extern int vrange_fork(struct mm_struct *new,
struct mm_struct *old);
diff --git a/mm/mmap.c b/mm/mmap.c
index 9d548512ff8a..b8e2c1e57336 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -36,6 +36,7 @@
#include <linux/sched/sysctl.h>
#include <linux/notifier.h>
#include <linux/memory.h>
+#include <linux/vrange.h>

#include <asm/uaccess.h>
#include <asm/cacheflush.h>
@@ -1503,6 +1504,10 @@ unsigned long mmap_region(struct file *file, unsigned long addr,
/* Clear old maps */
error = -ENOMEM;
+ /* zap any volatile ranges */
+ vrange_clear(&mm->vroot, addr, addr + len);
if (find_vma_links(mm, addr, addr + len, &prev, &rb_link, &rb_parent)) {
if (do_munmap(mm, addr, len))
return -ENOMEM;
diff --git a/mm/vrange.c b/mm/vrange.c
index 57dad4d72b04..444da8794dbf 100644
--- a/mm/vrange.c
+++ b/mm/vrange.c
@@ -167,6 +167,14 @@ static int vrange_remove(struct vrange_root *vroot,
return 0;

+int vrange_clear(struct vrange_root *vroot,
+ unsigned long start, unsigned long end)
+ int purged;
+ return vrange_remove(vroot, start, end - 1, &purged);
void vrange_root_cleanup(struct vrange_root *vroot)
struct vrange *range;

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/