From: Oleg Nesterov <oleg@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jeff Dike <jdike@addtoit.com>,
utrace-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC, PATCH 0/2] utrace/ptrace: simplify/cleanup ptrace attach
Date: Mon, 4 May 2009 21:30:16 +0200 [thread overview]
Message-ID: <20090504193016.GA17076@redhat.com> (raw)
In-Reply-To: <20090504184951.623CEFC32F@magilla.sf.frob.com>
On 05/04, Roland McGrath wrote:
>
> I guess I'm slightly confused.
Me too ;)
> We want to merge all of the "pure" ptrace
> cleanup patches before any utrace patch.
Yes, exactly!
The second patch "ptrace: do not use task_lock() for attach" has nothing
to do with utrace, and it is really pure ptrace cleanup.
But it can't be applied to -mm tree, because it (textually) conficts with
utrace changes in ptrace_attach().
> When those are on their way,
> we'll update the utrace patches not to conflict. I don't think it makes
> sense to include utrace.patch's little ptrace.c change in the baseline tree
> for your ptrace cleanup patches.
Yes, but in this case, how can we push it before utrace-core.patch ?
The first patch is only for -mm, to avoid the painful dependencies.
Since you seem to mostly agree with the second patch, what should I do?
Oleg.
next prev parent reply other threads:[~2009-05-04 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 18:55 [RFC, PATCH 0/2] utrace/ptrace: simplify/cleanup ptrace attach Oleg Nesterov
2009-05-04 18:49 ` Roland McGrath
2009-05-04 19:30 ` Oleg Nesterov [this message]
2009-05-04 19:43 ` Roland McGrath
2009-05-04 23:31 ` Andrew Morton
2009-05-05 1:12 ` Roland McGrath
2009-05-05 23:06 ` Oleg Nesterov
2009-05-06 8:12 ` Ingo Molnar
2009-05-06 8:23 ` Christoph Hellwig
2009-05-06 9:05 ` Ingo Molnar
2009-05-06 9:11 ` Christoph Hellwig
2009-05-06 9:37 ` Ingo Molnar
2009-05-07 6:13 ` Roland McGrath
2009-05-08 15:08 ` 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=20090504193016.GA17076@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=utrace-devel@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