From: Christoph Hellwig <hch@infradead.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Denys Vlasenko <vda.linux@googlemail.com>,
Tejun Heo <tj@kernel.org>,
Vladimir Zapolskiy <vzapolskiy@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ptrace changes for v3.1
Date: Fri, 22 Jul 2011 14:03:12 -0400 [thread overview]
Message-ID: <20110722180312.GA744@infradead.org> (raw)
In-Reply-To: <20110722173237.GA16787@redhat.com>
On Fri, Jul 22, 2011 at 07:32:37PM +0200, Oleg Nesterov wrote:
> - f701e5b7 "connector: add an event for monitoring process tracers" is
> a bit off-topic, it was routed via ptrace branch because it textually
> depends on the changes in tracehook/ptrace_attach code.
Please do not actually add anything to the connector code. It's a
horrible interface and users should migrate away from it.
next prev parent reply other threads:[~2011-07-22 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 17:32 [GIT PULL] ptrace changes for v3.1 Oleg Nesterov
2011-07-22 18:03 ` Christoph Hellwig [this message]
2011-07-22 18:09 ` Randy Dunlap
2011-07-22 18:20 ` Oleg Nesterov
2011-07-22 19:07 ` Evgeniy Polyakov
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=20110722180312.GA744@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.com \
--cc=vzapolskiy@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.