linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Doug Doan <dougd@cray.com>
To: linux-mm@kvack.org
Subject: Bug in hugetlb_cow()?
Date: Wed, 26 May 2010 14:57:39 -0700	[thread overview]
Message-ID: <4BFD9953.8080408@cray.com> (raw)

Hi,

I'm working on a driver that relies on mmu notifications, and found that it is 
lacking for huge pages.

 From handle_mm_fault(),

If we take the normal page path, this is what happens:

handle_pte_fault -> do_wp_page -> ptep_clear_flush_notify -> 
mmu_notifier_invalidate_page

If we're dealing with huge pages, this is what happens:

hugetlb_fault -> hugetlb_cow -> (no mmu notifiers)

Below is my patch, can anyone comment?

diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index 4c9e6bb..96d9937 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -2345,11 +2345,17 @@ retry_avoidcopy:
         ptep = huge_pte_offset(mm, address & huge_page_mask(h));
         if (likely(pte_same(huge_ptep_get(ptep), pte))) {
                 /* Break COW */
+               mmu_notifier_invalidate_range_start(mm,
+                       address & huge_page_mask(h),
+                       (address & huge_page_mask(h)) + huge_page_size(h));
                 huge_ptep_clear_flush(vma, address, ptep);
                 set_huge_pte_at(mm, address, ptep,
                                 make_huge_pte(vma, new_page, 1));
                 /* Make the old page be freed below */
                 new_page = old_page;
+               mmu_notifier_invalidate_range_end(mm,
+                       address & huge_page_mask(h),
+                       (address & huge_page_mask(h)) + huge_page_size(h));
         }
         page_cache_release(new_page);
         page_cache_release(old_page);

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2010-05-26 21:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4BFD9953.8080408@cray.com \
    --to=dougd@cray.com \
    --cc=linux-mm@kvack.org \
    /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).