From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: James Morris <jmorris@namei.org>,
Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm_for_maps: shift down_read(mmap_sem) to the caller
Date: Thu, 9 Jul 2009 22:06:33 -0500 [thread overview]
Message-ID: <20090710030633.GA11280@us.ibm.com> (raw)
In-Reply-To: <20090710012738.GA392@redhat.com>
Quoting Oleg Nesterov (oleg@redhat.com):
> mm_for_maps() takes ->mmap_sem after security checks, this looks
> strange and obfuscates the locking rules. Move this lock to its
> single caller, m_start().
>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Looks sane.
Acked-by: Serge Hallyn <serue@us.ibm.com>
> ---
>
> fs/proc/task_mmu.c | 1 +
> fs/proc/task_nommu.c | 1 +
> fs/proc/base.c | 8 +++-----
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> --- WAIT/fs/proc/task_mmu.c~1_MOVE_MMAP_SEM 2009-05-03 17:15:27.000000000 +0200
> +++ WAIT/fs/proc/task_mmu.c 2009-07-10 02:00:56.000000000 +0200
> @@ -119,6 +119,7 @@ static void *m_start(struct seq_file *m,
> mm = mm_for_maps(priv->task);
> if (!mm)
> return NULL;
> + down_read(&mm->mmap_sem);
>
> tail_vma = get_gate_vma(priv->task);
> priv->tail_vma = tail_vma;
> --- WAIT/fs/proc/task_nommu.c~1_MOVE_MMAP_SEM 2009-04-09 00:39:09.000000000 +0200
> +++ WAIT/fs/proc/task_nommu.c 2009-07-10 02:01:25.000000000 +0200
> @@ -189,6 +189,7 @@ static void *m_start(struct seq_file *m,
> priv->task = NULL;
> return NULL;
> }
> + down_read(&mm->mmap_sem);
>
> /* start from the Nth VMA */
> for (p = rb_first(&mm->mm_rb); p; p = rb_next(p))
> --- WAIT/fs/proc/base.c~1_MOVE_MMAP_SEM 2009-07-09 17:56:27.000000000 +0200
> +++ WAIT/fs/proc/base.c 2009-07-10 02:05:14.000000000 +0200
> @@ -235,9 +235,8 @@ static int check_mem_permission(struct t
> struct mm_struct *mm_for_maps(struct task_struct *task)
> {
> struct mm_struct *mm = get_task_mm(task);
> - if (!mm)
> - return NULL;
> - if (mm != current->mm) {
> +
> + if (mm && mm != current->mm) {
> /*
> * task->mm can be changed before security check,
> * in that case we must notice the change after.
> @@ -245,10 +244,9 @@ struct mm_struct *mm_for_maps(struct tas
> if (!ptrace_may_access(task, PTRACE_MODE_READ) ||
> mm != task->mm) {
> mmput(mm);
> - return NULL;
> + mm = NULL;
> }
> }
> - down_read(&mm->mmap_sem);
> return mm;
> }
>
prev parent reply other threads:[~2009-07-10 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 1:27 [PATCH 1/2] mm_for_maps: shift down_read(mmap_sem) to the caller Oleg Nesterov
2009-07-10 3:06 ` Serge E. Hallyn [this message]
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=20090710030633.GA11280@us.ibm.com \
--to=serue@us.ibm.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=roland@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