From: Ray Bryant <raybry@sgi.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>
Cc: Marcello Tosatti <marcelo.tosatti@cyclades.com>,
Dave Hansen <haveblue@us.ibm.com>, linux-mm <linux-mm@kvack.org>
Subject: [PATCH] mm: memory migration: bug in touch_unmapped_address
Date: Mon, 28 Feb 2005 11:36:43 -0600 [thread overview]
Message-ID: <422356AB.4040703@sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
Hirokazu,
The length field in the call to get_user_pages() from touch_unmapped_pages()
is incorrectly specified in bytes, not pages.
As a result of this, if you use the migration code to migrate a page, then
subsequent pages (that are not necessarily currently allocated or mapped)
can be allocated and mapped as a result of the migration call.
[touch_unmapped_pages() is added by the memory migration code from the memory
hotplug patch so this is not currently part of the mainline kernel]
See attached patch for the fix.
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
[-- Attachment #2: fix-len-param-in-touch_unmapped_address.patch --]
[-- Type: text/plain, Size: 1067 bytes --]
The "len" parameter (4th arg) of get_user_pages() is in pages, not
bytes. The effect of this bug is that if you migrate a page, and
if this page is followed by valid virtual addresses, but these
pages have not yet been touched and allocated, then the migration
call will cause those pages to be touched and allocated. The number
of pages so effected is the min of (16384, the remaining number of
pages in the vma, the number of pages required to fill out the
current pmd).
Signed-off-by: Ray Bryant <raybry@sgi.com>
Index: linux/mm/rmap.c
===================================================================
--- linux.orig/mm/rmap.c 2005-01-30 10:34:03.000000000 -0800
+++ linux/mm/rmap.c 2005-02-28 08:53:30.000000000 -0800
@@ -554,8 +554,7 @@ touch_unmapped_address(struct list_head
vma = find_vma(v1->mm, v1->addr);
if (vma == NULL)
goto out;
- error = get_user_pages(current, v1->mm, v1->addr, PAGE_SIZE,
- 0, 0, NULL, NULL);
+ error = get_user_pages(current, v1->mm, v1->addr, 1, 0, 0, NULL, NULL);
if (error < 0)
ret = error;
out:
next reply other threads:[~2005-02-28 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 17:36 Ray Bryant [this message]
2005-02-28 13:33 ` Marcelo Tosatti
2005-02-28 18:56 ` Ray Bryant
2005-03-01 0:09 ` Hirokazu Takahashi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=422356AB.4040703@sgi.com \
--to=raybry@sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=taka@valinux.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox