From: Tejun Heo <tj@kernel.org>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Why I want PTRACE_O_TRACESTOP option
Date: Sun, 11 Sep 2011 09:58:04 +0900 [thread overview]
Message-ID: <20110911005804.GF29319@htj.dyndns.org> (raw)
In-Reply-To: <201109090754.50272.vda.linux@googlemail.com>
Hello, Denys.
On Fri, Sep 09, 2011 at 07:54:50AM +0200, Denys Vlasenko wrote:
> My point is that previously, ptrace behavior was modified by setting
> options. Why don't we use this mechanism? Why we invent a different
> wheel? Ptrace is ugly as-is, why complicate it even further?
>
> The argument was that SETOPTIONS wasn't suitable for modifying
> attach behavior, but this is fixed by "set options on SEIZE"
> patch. I don't see why we can't use options mechanist to affect
> group-stop behavior now.
The argument was that there are other more difficult issues and the
added benefit - superficial consistency - doesn't justify the
necessary complexity, and it was repeated multiple times.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-09-11 0:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 16:50 Why I want PTRACE_O_TRACESTOP option Denys Vlasenko
2011-09-09 0:18 ` Tejun Heo
2011-09-09 5:45 ` Denys Vlasenko
2011-09-09 16:00 ` Oleg Nesterov
2011-09-10 23:43 ` Tejun Heo
2011-09-09 5:54 ` Denys Vlasenko
2011-09-09 12:26 ` Indan Zupancic
2011-09-09 13:01 ` Indan Zupancic
2011-09-09 16:46 ` Denys Vlasenko
2011-09-09 16:26 ` Oleg Nesterov
2011-09-09 23:09 ` Indan Zupancic
2011-09-10 1:17 ` Denys Vlasenko
2011-09-10 11:20 ` Pedro Alves
2011-09-11 0:58 ` Tejun Heo [this message]
2011-09-09 16:14 ` 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=20110911005804.GF29319@htj.dyndns.org \
--to=tj@kernel.org \
--cc=dvlasenk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=vda.linux@googlemail.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.