mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: dhowells@redhat.com, Roland McGrath <roland@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Frysinger <vapier@gentoo.org>,
	linux-sh@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
	uclinux-dist-devel@blackfin.uclinux.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 1/1] ptrace: PTRACE_GETFDPIC: fix the unsafe usage of child->mm
Date: Mon, 24 May 2010 15:36:57 +0100	[thread overview]
Message-ID: <25539.1274711817@redhat.com> (raw)
In-Reply-To: <20100522165401.GB19573@redhat.com>

Oleg Nesterov <oleg@redhat.com> wrote:

> Now that Mike Frysinger unified the FDPIC ptrace code, we can fix
> the unsafe usage of child->mm in ptrace_request(PTRACE_GETFDPIC).
> 
> We have the reference to task_struct, and ptrace_check_attach()
> verified the tracee is stopped. But nothing can protect from
> SIGKILL after that, we must not assume child->mm != NULL.
> 
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>

Acked-by: David Howells <dhowells@redhat.com>

Does it make sense to move the call to get_task_mm() up to sys_ptrace() since
several ptrace functions use it?  The mm pointer could then be handed down the
ptrace hierarchy.

David

  parent reply	other threads:[~2010-05-24 14:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  0:30 [PATCH] ptrace: unify FDPIC implementations Mike Frysinger
2010-02-16  1:10 ` Paul Mundt
2010-02-16  8:12   ` Mike Frysinger
2010-05-21  8:42 ` [PATCH v2] " Mike Frysinger
2010-05-21 16:26   ` Oleg Nesterov
2010-05-21 18:35     ` Roland McGrath
2010-05-22 16:53       ` [PATCH -mm 0/1] (Was: ptrace: unify FDPIC implementations) Oleg Nesterov
2010-05-22 16:54         ` [PATCH -mm 1/1] ptrace: PTRACE_GETFDPIC: fix the unsafe usage of child->mm Oleg Nesterov
2010-05-24  4:33           ` [Uclinux-dist-devel] " Mike Frysinger
2010-05-24  8:38           ` Roland McGrath
2010-05-24 14:36         ` David Howells [this message]
2010-05-24 15:14           ` Oleg Nesterov
2010-05-24 23:42             ` Roland McGrath
2010-05-25  1:29               ` [Uclinux-dist-devel] " Mike Frysinger
2010-05-25 19:11                 ` Roland McGrath
2010-05-25  9:14             ` David Howells
2010-05-25 10:23               ` Oleg Nesterov
2010-05-25 17:28                 ` Mike Frysinger
2010-05-26 12:40                   ` Oleg Nesterov
2010-05-27 19:55                     ` [PATCH 0/2] blackfin: ptrace mm/sram_list fixes Oleg Nesterov
2010-05-27 19:56                       ` [PATCH 1/2] blackfin: ptrace: fix the unsafe usage of mm/find_vma in is_user_addr_valid() Oleg Nesterov
2010-05-27 19:56                       ` [PATCH 2/2] blackfin: use ->mmap_sem to protect mm_context_t->sram_list Oleg Nesterov
2010-05-27 20:21                       ` [PATCH 0/2] blackfin: ptrace mm/sram_list fixes Mike Frysinger
2010-05-28 19:43                         ` Oleg Nesterov
2010-05-25 12:24               ` [PATCH -mm 1/1] ptrace: PTRACE_GETFDPIC: fix the unsafe usage of child->mm David Howells
2010-05-25 12:30                 ` Oleg Nesterov

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=25539.1274711817@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=roland@redhat.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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

Powered by JetHome