linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
	n-horiguchi@ah.jp.nec.com
Subject: Re: [PATCH] Fix virtual address handling in hugetlb fault
Date: Mon, 21 Nov 2011 14:27:20 -0800	[thread overview]
Message-ID: <20111121142720.a5b62c9c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20111121194832.a0026d3e.kamezawa.hiroyu@jp.fujitsu.com>

On Mon, 21 Nov 2011 19:48:32 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:

> >From 7c29389be2890c6b6934a80b4841d07a7014fe26 Mon Sep 17 00:00:00 2001
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Date: Mon, 21 Nov 2011 19:45:27 +0900
> Subject: [PATCH] Fix virtual address handling in hugetlb fault
> 
> handle_mm_fault() passes 'faulted' address to hugetlb_fault().
> Then, the address is not aligned to hugepage boundary.
> 
> Most of functions for hugetlb pages are aware of that and
> calculate an alignment by itself. Some functions as copy_user_huge_page(),
> and clear_huge_page() doesn't handle alignment by themselves.
> 
> This patch make hugeltb_fault() to calculate the alignment and pass
> aligned addresss (top address of a faulted hugepage) to functions.
> 

Does this actually fix any known user-visible misbehaviour?

It sounds like the code is masking addresses in a lot of different
places.  It would be better to do it once, at the top level.  Perhaps
this patch makes some of the existing masking obsolete?

> index bb28a5f..af37337 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -2629,6 +2629,8 @@ int hugetlb_fault(struct mm_struct *mm, struct vm_area_struct *vma,
>  	static DEFINE_MUTEX(hugetlb_instantiation_mutex);
>  	struct hstate *h = hstate_vma(vma);
>  
> +	address = address & huge_page_mask(h);

--- a/mm/hugetlb.c~mm-hugetlbc-fix-virtual-address-handling-in-hugetlb-fault-fix
+++ a/mm/hugetlb.c
@@ -2639,7 +2639,7 @@ int hugetlb_fault(struct mm_struct *mm, 
 	static DEFINE_MUTEX(hugetlb_instantiation_mutex);
 	struct hstate *h = hstate_vma(vma);
 
-	address = address & huge_page_mask(h);
+	address &= huge_page_mask(h);
 
 	ptep = huge_pte_offset(mm, address);
 	if (ptep) {

is a bit more readable, IMO.

--
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 internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-11-21 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 10:48 [PATCH] Fix virtual address handling in hugetlb fault KAMEZAWA Hiroyuki
2011-11-21 22:27 ` Andrew Morton [this message]
2011-11-22  0:32   ` KAMEZAWA Hiroyuki
2011-11-22  0:36     ` Andrew Morton

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=20111121142720.a5b62c9c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --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;
as well as URLs for NNTP newsgroup(s).