linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@engr.sgi.com>
To: Hugh Dickins <hugh@veritas.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 07:55:02 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0602270748280.2419@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0602261558370.13368@goblin.wat.veritas.com>

On Sun, 26 Feb 2006, Hugh Dickins wrote:

> On Sat, 25 Feb 2006, Christoph Lameter wrote:
> > Here is the parameterization you wanted. However, I am still not sure
> > that a check for a valid mapping here is sufficient if the caller has no
> > other means to guarantee that the mapping is not vanishing.
> > 
> > If the mapping is removed after the check for the mapping was done then
> > we still have a problem.
> > 
> > Or is there some way that RCU can preserve the existence of an anonymous 
> > vma?
> > 
> > Cannot imagine how that would work. If an rcu free was done on the 
> > anonymous vma then it may vanish anytime after page_lock_anon_vma does a 
> > rcu unlock. And then we are holding a lock that is located in free 
> > space...... 
> 
> Please see comments on SLAB_DESTROY_BY_RCU in mm/slab.c: that's why the
> anon_vma cache is created with that flag, that's why page_lock_anon_vma
> uses rcu_read_lock.  Your patch, with more appropriate comments and my
> signoff added, below (but, in case there's any doubt, it's not suitable
> for 2.6.16 - the change itself is simple, but it suddenly makes the
> hitherto untried codepaths of remove_from_swap accessible).

At least my tests show that this codepath is valid and its for new 
functionality in 2.6.16. So I guess its suitable for 2.6.16.

I doubt that RCU can help if the anon_vma is removed after the check for 
page_mapped. In that case RCU prevents the ultimate free from happening 
until rcu_read_unlock. So in essence we lock the anon_vma, return a 
pointer to the anonymous vma and then free the anon_vma? Functions calling 
page_lock_anon_vma may operate on freed memory due to this race.

Should we not check again for page_mapped after taking the lock?

--
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:[~2006-02-27 15:55 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 [this message]
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
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.64.0602270748280.2419@schroedinger.engr.sgi.com \
    --to=clameter@engr.sgi.com \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.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