From: Oleg Nesterov <oleg@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Denys Vlasenko <dvlasenk@redhat.com>,
linux-kernel@vger.kernel.org,
Denys Vlasenko <vda.linux@googlemail.com>
Subject: Re: Why I want PTRACE_O_TRACESTOP option
Date: Fri, 9 Sep 2011 18:14:59 +0200 [thread overview]
Message-ID: <20110909161459.GB23271@redhat.com> (raw)
In-Reply-To: <20110909001853.GA29319@htj.dyndns.org>
On 09/09, Tejun Heo wrote:
>
> To me, the rationale presented here almost argues against
> PTRACE_O_TRACESTOP. :(
Personally I dislike PTRACE_O_TRACESTOP too.
And once again, this needs more (nontrivial) changes than just
s/PT_SEIZED/PTRACE_O_TRACESTOP/, the patch was wrong.
And, just for example. While this is minor, I'd like to improve
the error codes from ptrace_check_attach(). Until we drop
PTRACE_SEIZE_DEVEL we can safely do this. I don't think it makes
sense to add the new PTRACE_O for this.
And finally, I simply do not understand how it can be useful.
Oleg.
prev parent reply other threads:[~2011-09-09 16:18 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
2011-09-09 16:14 ` Oleg Nesterov [this message]
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=20110909161459.GB23271@redhat.com \
--to=oleg@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--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.