From: Andrew Morton <akpm@linux-foundation.org>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>,
Larry Woodman <lwoodman@redhat.com>,
Rik van Riel <riel@redhat.com>,
Ulrich Obergfell <uobergfe@redhat.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Subject: Re: [PATCH] mm: thp: fix pmd_bad() triggering in code paths holding mmap_sem read mode
Date: Thu, 15 Mar 2012 16:27:11 -0700 [thread overview]
Message-ID: <20120315162711.0870c27b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120315231556.GA24602@redhat.com>
On Fri, 16 Mar 2012 00:15:56 +0100
Andrea Arcangeli <aarcange@redhat.com> wrote:
> On Thu, Mar 15, 2012 at 03:45:04PM -0700, Andrew Morton wrote:
> > Or do we still need pdm_trans_unstable() checking in
> > mem_cgroup_count_precharge_pte_range() and
> > mem_cgroup_move_charge_pte_range()?
>
> I think we need a pmd_trans_unstable check before the
> pte_offset_map_lock in both places. Otherwise with only the mmap_sem
> hold for reading, the pmd may have been transhuge,
> mem_cgroup_move_charge_pte_range could be called, and then
> MADV_DONTNEED would transform the pmd to none from another thread just
> before pmd_trans_huge_lock runs, and we would end up doing
> pmd_offset_map_lock on a none pmd (or a transhuge pmd if it becomes
> huge again before we get there).
page_table_lock doesn't prevent the race? pmd_trans_huge_lock()
rechecks after taking that lock...
> Only if pmd_trans_unstable is false, the pmd can't change from under
> us, so we can proceed safely with the pte level walk (and it just need
> to be checked with a compiler barrier, as the real pmd changes freely
> from under us).
>
> pmd_trans_unstable will never actually trigger unless we're hitting
> the race, if the pmd was none when we started the walk we'd abort at
> the higher level (method not called), if the pmd was transhuge we'd
> stop at the pmd_trans_huge_lock() == 1 branch. So the only way to run
> pmd_trans_unstable is when the result is undefined, i.e. the pmd was
> not none initially but it become none or transhuge or none again at
> some point, so we can just simply consider it still none and skip for
> the undefined case.
Naoya, could you please take a look into this?
--
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>
next prev parent reply other threads:[~2012-03-15 23:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 14:44 Andrea Arcangeli
2012-03-15 16:01 ` Rik van Riel
2012-03-15 16:13 ` Larry Woodman
2012-03-15 17:16 ` Dave Jones
2012-03-15 17:41 ` Andrea Arcangeli
2012-03-15 22:30 ` Andrew Morton
2012-03-15 18:08 ` Johannes Weiner
2012-03-15 22:45 ` Andrew Morton
2012-03-15 23:15 ` Andrea Arcangeli
2012-03-15 23:27 ` Andrew Morton [this message]
2012-03-16 8:05 ` Naoya Horiguchi
2012-03-16 11:54 ` Andrea Arcangeli
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=20120315162711.0870c27b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=mgorman@suse.de \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=riel@redhat.com \
--cc=uobergfe@redhat.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