[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1360056113-14294-3-git-send-email-linfeng@cn.fujitsu.com>
Date: Tue, 5 Feb 2013 17:21:53 +0800
From: Lin Feng <linfeng@...fujitsu.com>
To: akpm@...ux-foundation.org, mgorman@...e.de, bcrl@...ck.org,
viro@...iv.linux.org.uk
Cc: khlebnikov@...nvz.org, walken@...gle.com,
kamezawa.hiroyu@...fujitsu.com, minchan@...nel.org,
riel@...hat.com, rientjes@...gle.com,
isimatu.yasuaki@...fujitsu.com, wency@...fujitsu.com,
laijs@...fujitsu.com, jiang.liu@...wei.com, zab@...hat.com,
jmoyer@...hat.com, linux-mm@...ck.org, linux-aio@...ck.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Lin Feng <linfeng@...fujitsu.com>
Subject: [PATCH V2 2/2] fs/aio.c: use get_user_pages_non_movable() to pin ring pages when support memory hotremove
This patch gets around the aio ring pages can't be migrated bug caused by
get_user_pages() via using the new function. It only works as configed with
CONFIG_MEMORY_HOTREMOVE, otherwise it falls back to use the old version
of get_user_pages().
Cc: Benjamin LaHaise <bcrl@...ck.org>
Cc: Alexander Viro <viro@...iv.linux.org.uk>
Cc: Andrew Morton <akpm@...ux-foundation.org>
Cc: Jeff Moyer <jmoyer@...hat.com>
Cc: Minchan Kim <minchan@...nel.org>
Cc: Zach Brown <zab@...hat.com>
Reviewed-by: Tang Chen <tangchen@...fujitsu.com>
Reviewed-by: Gu Zheng <guz.fnst@...fujitsu.com>
Signed-off-by: Lin Feng <linfeng@...fujitsu.com>
---
fs/aio.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 71f613c..f7a0d5c 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -138,8 +138,8 @@ static int aio_setup_ring(struct kioctx *ctx)
}
dprintk("mmap address: 0x%08lx\n", info->mmap_base);
- info->nr_pages = get_user_pages(current, ctx->mm,
- info->mmap_base, nr_pages,
+ info->nr_pages = get_user_pages_non_movable(current, ctx->mm,
+ info->mmap_base, nr_pages,
1, 0, info->ring_pages, NULL);
up_write(&ctx->mm->mmap_sem);
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists