From: Evgeniy Polyakov <zbr@ioremap.net>
To: Vladimir Zapolskiy <vzapolskiy@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2] connector: add an event for monitoring process tracers
Date: Mon, 18 Jul 2011 20:15:58 +0400 [thread overview]
Message-ID: <20110718161558.GA366@ioremap.net> (raw)
In-Reply-To: <1310751918-31579-1-git-send-email-vzapolskiy@gmail.com>
Hi.
On Fri, Jul 15, 2011 at 08:45:18PM +0300, Vladimir Zapolskiy (vzapolskiy@gmail.com) wrote:
> This version of the change extends proc_ptrace_connector() argument
> list, so it becomes possible to specify a ptrace request eliminating
> process attach/detach race.
>
> Also tracehook_tracer_task() function was renamed to ptrace_parent(),
> but as far as proc_ptrace_connector(task, PTRACE_ATTACH) is called
> from a tracer process itself, it becomes possible to get rid of that
> call usage completely.
>
> Oleg, I've rebased the change, and if you don't have objections, I'd
> be glad, if you can apply this change upon your ptrace branch, thank
> you in advance.
I still ack this one :)
Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
--
Evgeniy Polyakov
next prev parent reply other threads:[~2011-07-18 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 17:45 [PATCH v2] connector: add an event for monitoring process tracers Vladimir Zapolskiy
2011-07-18 16:15 ` Evgeniy Polyakov [this message]
2011-07-18 17:14 ` Oleg Nesterov
2011-07-21 18:34 ` [PATCH 0/1] (Was: connector: add an event for monitoring process tracers) Oleg Nesterov
2011-07-21 18:35 ` [PATCH 1/1] proc_fork_connector: a lockless ->real_parent usage is not safe Oleg Nesterov
2011-07-18 17:54 ` [PATCH v2] connector: add an event for monitoring process tracers Oleg Nesterov
2011-07-18 18:57 ` Vladimir Zapolskiy
2011-07-18 19:39 ` 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=20110718161558.GA366@ioremap.net \
--to=zbr@ioremap.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.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.