mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-sh@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
	uclinux-dist-devel@blackfin.uclinux.org,
	linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v2] ptrace: unify FDPIC implementations
Date: Fri, 21 May 2010 11:35:12 -0700 (PDT)	[thread overview]
Message-ID: <20100521183512.4477F40476@magilla.sf.frob.com> (raw)
In-Reply-To: Oleg Nesterov's message of  Friday, 21 May 2010 18:26:59 +0200 <20100521162659.GA16193@redhat.com>

> This looks unsafe. What protect child->mm if ptrace() races with SIGKILL ?
> 
> Of course, I do not blame this patch, the code was copied from arch/, but
> I think we need another patch which checks ->mm != NULL under task_lock()
> on top of this one?

Agreed, unless things are somehow different on nommu so there aren't such
races.  But, as you mention, this is a long-standing issue that is entirely 
unrelated to the cleanup here and should not delay merging this patch.


Thanks,
Roland

  reply	other threads:[~2010-05-21 18:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  0:30 [PATCH] " 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 [this message]
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
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=20100521183512.4477F40476@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=oleg@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

all inboxes | Powered by JetHome®