linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Paul Jackson <pj@sgi.com>
Cc: Christoph Lameter <clameter@engr.sgi.com>, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] Fold numa_maps into mempolicy.c
Date: Wed, 16 Nov 2005 09:36:04 +0100	[thread overview]
Message-ID: <200511160936.04721.ak@suse.de> (raw)
In-Reply-To: <20051115231051.5437e25b.pj@sgi.com>

On Wednesday 16 November 2005 08:10, Paul Jackson wrote:
> Christoph wrote:
> > + * Must hold mmap_sem until memory pointer is no longer in use
> > + * or be called from the current task.
> > + */
> > +struct mempolicy *get_vma_policy(struct task_struct *task,
> 
> Twenty (well, four) questions time.
> 
> Hmmm ... is that true - that get_vma_policy() can be called for the
> current task w/o holding mmap_sem?

Yes, e.g. when vma is NULL.

> Is there any call to get_vma_policy() made that isn't holding mmap_sem?

There are some callers of alloc_page_vma with NULL vma yes

> Except for /proc output, is there any call to get_vma_policy made on any
> task other than current?

In the original version there wasn't any. I still think it's a mistake
to allow it for /proc, unfortunately the patch went in.

> What does "until memory pointer is no longer in use" mean?

mempolicy is no longer in use or you took a reference.


-Andi
 

--
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:[~2005-11-16  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 23:24 [PATCH 1/2] private pointer in check_range and MPOL_MF_INVERT Christoph Lameter
2005-11-08 23:25 ` [PATCH 2/2] Fold numa_maps into mempolicy.c Christoph Lameter
2005-11-16  7:10   ` Paul Jackson
2005-11-16  8:36     ` Andi Kleen [this message]
2005-11-16 18:54       ` Christoph Lameter
2005-11-16 19:43         ` Paul Jackson
2005-11-16 18:21     ` Christoph Lameter

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=200511160936.04721.ak@suse.de \
    --to=ak@suse.de \
    --cc=clameter@engr.sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.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