From: Hugh Dickins <hugh@veritas.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: akpm@osdl.org, linux-mm@kvack.org
Subject: Re: page_lock_anon_vma(): remove check for mapped page
Date: Mon, 27 Feb 2006 18:27:18 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0602271823260.9352@goblin.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602270934260.3185@schroedinger.engr.sgi.com>
On Mon, 27 Feb 2006, Christoph Lameter wrote:
> On Mon, 27 Feb 2006, Hugh Dickins wrote:
>
> > > Or better do the rcu locking before calling page_lock_anon_vma
> > > and the unlocking after spin_unlock to have proper nesting of locks?
> >
> > No, page_lock_anon_vma is all about insulating the rest of the code
> > from these difficulties: I do prefer it as is.
>
> Hmm... How about page_lock_anon_vma and page_unlock_anon_vma? This
>
> I fear that code reviewers will not realize that the freeing of the
> anon_vma is in fact delayed much longer than a superficial review of the
> page_lock_anon_vma reveals.
>
> How about this patch:
I'd prefer not myself, perhaps someone else likes it.
And you haven't even based it on the check_mapped version you sent me,
which I then returned to you with more helpful comments.
Let's just move on?
Hugh
--
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:[~2006-02-27 18:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 1:03 Christoph Lameter
2006-02-25 14:01 ` Hugh Dickins
2006-02-26 4:42 ` Hugh Dickins
2006-02-26 5:26 ` Christoph Lameter
2006-02-26 15:58 ` Hugh Dickins
2006-02-27 15:47 ` Christoph Lameter
2006-02-26 5:57 ` Christoph Lameter
2006-02-26 16:07 ` Hugh Dickins
2006-02-27 15:55 ` Christoph Lameter
2006-02-27 16:32 ` Hugh Dickins
2006-02-27 16:43 ` Christoph Lameter
2006-02-27 17:23 ` Hugh Dickins
2006-02-27 18:11 ` Christoph Lameter
2006-02-27 18:27 ` Hugh Dickins [this message]
2006-02-27 18:31 ` Christoph Lameter
2006-02-27 18:43 ` Hugh Dickins
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=Pine.LNX.4.61.0602271823260.9352@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.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