From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jun'ichi Nomura <j-nomura@ce.jp.nec.com>,
Matt Mackall <mpm@selenic.com>
Subject: Re: [BUGFIX][PATCH] pagemap: set pagemap walk limit to PMD boundary
Date: Mon, 22 Nov 2010 12:01:02 +0900 [thread overview]
Message-ID: <20101122120102.e0e76373.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1290157665-17215-1-git-send-email-n-horiguchi@ah.jp.nec.com>
On Fri, 19 Nov 2010 18:07:45 +0900
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> wrote:
> Currently one pagemap_read() call walks in PAGEMAP_WALK_SIZE bytes
> (== 512 pages.) But there is a corner case where walk_pmd_range()
> accidentally runs over a VMA associated with a hugetlbfs file.
>
> For example, when a process has mappings to VMAs as shown below:
>
> # cat /proc/<pid>/maps
> ...
> 3a58f6d000-3a58f72000 rw-p 00000000 00:00 0
> 7fbd51853000-7fbd51855000 rw-p 00000000 00:00 0
> 7fbd5186c000-7fbd5186e000 rw-p 00000000 00:00 0
> 7fbd51a00000-7fbd51c00000 rw-s 00000000 00:12 8614 /hugepages/test
>
> then pagemap_read() goes into walk_pmd_range() path and walks in the range
> 0x7fbd51853000-0x7fbd51a53000, but the hugetlbfs VMA should be handled
> by walk_hugetlb_range(). Otherwise PMD for the hugepage is considered bad
> and cleared, which causes undesirable results.
>
> This patch fixes it by separating pagemap walk range into one PMD.
>
> Signed-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Cc: Matt Mackall <mpm@selenic.com>
> ---
> fs/proc/task_mmu.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
> index da6b01d..c126c83 100644
> --- a/fs/proc/task_mmu.c
> +++ b/fs/proc/task_mmu.c
> @@ -706,6 +706,7 @@ static int pagemap_hugetlb_range(pte_t *pte, unsigned long hmask,
> * skip over unmapped regions.
> */
> #define PAGEMAP_WALK_SIZE (PMD_SIZE)
> +#define PAGEMAP_WALK_MASK (PMD_MASK)
> static ssize_t pagemap_read(struct file *file, char __user *buf,
> size_t count, loff_t *ppos)
> {
> @@ -776,7 +777,7 @@ static ssize_t pagemap_read(struct file *file, char __user *buf,
> unsigned long end;
>
> pm.pos = 0;
> - end = start_vaddr + PAGEMAP_WALK_SIZE;
> + end = (start_vaddr + PAGEMAP_WALK_SIZE) & PAGEMAP_WALK_MASK;
> /* overflow ? */
> if (end < start_vaddr || end > end_vaddr)
> end = end_vaddr;
Ack.
But ALIGN() can't be used ?
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-22 3:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 9:07 Naoya Horiguchi
2010-11-22 3:01 ` KAMEZAWA Hiroyuki [this message]
2010-11-22 4:09 ` Naoya Horiguchi
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=20101122120102.e0e76373.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=n-horiguchi@ah.jp.nec.com \
/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