From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Lameter <cl@linux.com>
Cc: Hugh Dickins <hughd@google.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: fix hang on anon_vma->root->lock
Date: Sat, 28 Aug 2010 12:17:06 +0200 [thread overview]
Message-ID: <1282990626.1975.3270.camel@laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1008272136220.28501@router.home>
On Fri, 2010-08-27 at 21:47 -0500, Christoph Lameter wrote:
>
> I'd be much more comfortable if the following would be done
>
> A. Pin the anon_vma by either
> I. Take a refcount on the anon vma
My preemptible mmu patches do that..
> II. Take a lock in the anon vma (something that is not pointed to)
>
> B. Either
> I. All values that have been used before the pinning are
> verified after the pinning (and the lock is reacquired
> if verification fails).
>
> II. Or all functions using page_lock_anon_vma() must securely
> work in the case that the anon_vma was reused for
> something else before the vma lock was acquired.
Last time I looked they all work like that, they all use something akin
to vma_address() which validates that the page we're interested in is
indeed part of the vma we obtained from the rmap chain.
Anyway, I'll try and refresh my preemptible mmu patch-set now that the
merge window dust settled and post if again, hopefully we can stick it
in -next.
--
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>
next prev parent reply other threads:[~2010-08-28 10:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 6:12 Hugh Dickins
2010-08-26 6:41 ` David Miller
2010-08-26 10:54 ` Hugh Dickins
2010-08-26 19:00 ` David Miller
2010-08-27 0:19 ` Andrea Arcangeli
2010-08-26 13:32 ` Rik van Riel
2010-08-26 23:50 ` Andrea Arcangeli
2010-08-27 1:43 ` Hugh Dickins
2010-08-27 9:55 ` Andrea Arcangeli
2010-08-27 16:43 ` Hugh Dickins
2010-08-27 17:13 ` Christoph Lameter
2010-08-27 17:55 ` Hugh Dickins
2010-08-27 19:29 ` Christoph Lameter
2010-08-27 20:14 ` Hugh Dickins
2010-08-27 20:56 ` Christoph Lameter
2010-08-27 21:28 ` Hugh Dickins
2010-08-27 21:33 ` Hugh Dickins
2010-08-27 23:06 ` Christoph Lameter
2010-08-28 1:07 ` Hugh Dickins
2010-08-28 2:47 ` Christoph Lameter
2010-08-28 10:17 ` Peter Zijlstra [this message]
2010-08-28 15: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=1282990626.1975.3270.camel@laptop \
--to=peterz@infradead.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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