From: Markus Metzger <markus.t.metzger@googlemail.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: "Metzger, Markus T" <markus.t.metzger@intel.com>,
Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Markus Metzger <markus.t.metzger@googlemail.com>
Subject: Re: [PATCH, for 2.6.29] ptrace: fix the usage of ptrace_fork()
Date: Tue, 10 Feb 2009 21:21:59 +0100 [thread overview]
Message-ID: <1234297319.6112.23.camel@raistlin> (raw)
In-Reply-To: <20090210184014.GA30545@redhat.com>
On Tue, 2009-02-10 at 19:40 +0100, Oleg Nesterov wrote:
> > 2. there is a race between a thread detaching
> > and another thread releasing the same task.
I think I now see the problem. Ptrace uses the tasklist_lock to protect
against __ptrace_unlink() races.
I could either introduce a separate lock to protect bts buffer
deallocation, or I put the kfree part under the tasklist_lock,
as you suggest below.
> Perhaps, for 2.6.29, we can do something like the "patch" below?
>
> (btw, do you agree with the change in copy_process() I sent? )
Both patches look good to me.
> --- a/arch/x86/kernel/ptrace.c
> +++ b/arch/x86/kernel/ptrace.c
> @@ -810,11 +810,15 @@ static void ptrace_bts_untrace(struct ta
>
> static void ptrace_bts_detach(struct task_struct *child)
> {
> + // We can race with de_thread/do_wait which
> + // can do ptrace_bts_untrace() before us
> if (unlikely(child->bts)) {
> - ds_release_bts(child->bts);
> - child->bts = NULL;
> -
> - ptrace_bts_free_buffer(child);
> + // This all will be freed by ptrace_bts_untrace()
> + // later, but we should update ->mm
> + down_write(->mmap_sem);
> + mm->total_vm -= bts_size;
> + mm->locked_vm -= bts_size);
> + up_write(->mmap_sem);
> }
> }
> #else
>
You already sent out the first one. I don't have access to any
test machine from home. I could send the patch tomorrow (evening).
thanks and regards,
markus.
next prev parent reply other threads:[~2009-02-10 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 1:02 [PATCH, for 2.6.29] ptrace: fix the usage of ptrace_fork() Oleg Nesterov
2009-02-09 1:28 ` Oleg Nesterov
2009-02-09 1:54 ` Roland McGrath
2009-02-09 9:28 ` Metzger, Markus T
2009-02-09 19:36 ` Oleg Nesterov
2009-02-10 9:47 ` Metzger, Markus T
2009-02-10 18:40 ` Oleg Nesterov
2009-02-10 20:21 ` Markus Metzger [this message]
2009-02-10 21:00 ` Markus Metzger
2009-02-10 21:48 ` Oleg Nesterov
2009-02-11 7:03 ` Markus Metzger
2009-02-10 20:08 ` Andrew Morton
2009-02-11 9:33 ` Ingo Molnar
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=1234297319.6112.23.camel@raistlin \
--to=markus.t.metzger@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--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