From: Serge Hallyn <serge.hallyn@canonical.com>
To: Tejun Heo <tj@kernel.org>
Cc: Pavel Emelyanov <xemul@parallels.com>,
Nathan Lynch <ntl@pobox.com>, Oren Laadan <orenl@cs.columbia.edu>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
Serge Hallyn <serge@hallyn.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Glauber Costa <glommer@parallels.com>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Containers <containers@lists.osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [EXAMPLE CODE] Parasite thread injection using PTRACE_SEIZE and friends
Date: Wed, 20 Jul 2011 09:21:29 -0500 [thread overview]
Message-ID: <20110720142129.GB19603@peqn> (raw)
In-Reply-To: <20110720140335.GN3455@htj.dyndns.org>
Quoting Tejun Heo (tj@kernel.org):
> On Wed, Jul 20, 2011 at 04:00:37PM +0200, Tejun Heo wrote:
> > With new ptrace requests, a process can be captured and manipulated
> > practically transparently. Other than syscall retry or -EINTR failure
> > in special cases and timing difference, everything including job
> > control stop state stays transparent across ptrace operations.
>
> Ooh, forgot to mention something. The ptracer can also reliably
> determine whether job control stop is in effect or not, so the whole
> job control state can be captured.
It sounds cool, thanks. Is this completely separate from Pavel's
CR patchset (which I've not yet gotten around to looking at in
detail)?
-serge
next prev parent reply other threads:[~2011-07-20 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 14:00 Tejun Heo
2011-07-20 14:03 ` Tejun Heo
2011-07-20 14:21 ` Serge Hallyn [this message]
2011-07-20 14:23 ` Tejun Heo
2011-07-22 23:19 ` Matt Helsley
2011-07-23 2:10 ` Tejun Heo
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=20110720142129.GB19603@peqn \
--to=serge.hallyn@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=dlezcano@fr.ibm.com \
--cc=glommer@parallels.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntl@pobox.com \
--cc=oleg@redhat.com \
--cc=orenl@cs.columbia.edu \
--cc=serge@hallyn.com \
--cc=tj@kernel.org \
--cc=xemul@parallels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®