From: Oleg Nesterov <oleg@redhat.com>
To: Vladimir Zapolskiy <vzapolskiy@gmail.com>
Cc: netdev@vger.kernel.org, Evgeniy Polyakov <zbr@ioremap.net>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2] connector: add an event for monitoring process tracers
Date: Mon, 18 Jul 2011 19:54:58 +0200 [thread overview]
Message-ID: <20110718175458.GA12840@redhat.com> (raw)
In-Reply-To: <1310751918-31579-1-git-send-email-vzapolskiy@gmail.com>
On 07/15, Vladimir Zapolskiy wrote:
>
> Such an event allows to create a simple automated userspace mechanism
> to be aware about processes connecting to others, therefore predefined
> process policies can be applied to them if needed.
I'd wish I could understand this ;) IOW, I still do not understand why
this is useful, but this doesn't matter. Since Evgeniy acked this patch,
I'll apply it to ptrace tree.
Can't resist, a couple of very minor/cosmetics nits. Just because I am
blighter ;)
> +void proc_ptrace_connector(struct task_struct *task, int which_id);
"which_id" doesn't match "ptrace_id" used elsewhere. And PTRACE_ATTACH
instead of simple boolean looks as if you are going to add more ptrace
events, but I guess this won't happen.
> - if (!retval)
> + if (!retval) {
> wait_on_bit(&task->jobctl, JOBCTL_TRAPPING_BIT,
> ptrace_trapping_sleep_fn, TASK_UNINTERRUPTIBLE);
> + proc_ptrace_connector(task, PTRACE_ATTACH);
> + }
OK, but it is a bit strange we are waiting for STOPPED/TRACED transition
before we report PROC_EVENT_PTRACE. Perhaps it makes more sense to
call proc_ptrace_connector() first, this also decreases the probability
PTRACE_ATTACH will be reported after PROC_EVENT_EXIT.
But once again, this is very minor and cosmetic. I am going to apply
the patch as is unless you send v3 quickly.
Oleg.
next prev parent reply other threads:[~2011-07-18 17:57 UTC|newest]
Thread overview: 6+ 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
2011-07-18 17:14 ` Oleg Nesterov
2011-07-18 17:54 ` Oleg Nesterov [this message]
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=20110718175458.GA12840@redhat.com \
--to=oleg@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vzapolskiy@gmail.com \
--cc=zbr@ioremap.net \
/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;
as well as URLs for NNTP newsgroup(s).