From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751912Ab1GTODl (ORCPT ); Wed, 20 Jul 2011 10:03:41 -0400 Received: from mail-ey0-f171.google.com ([209.85.215.171]:64385 "EHLO mail-ey0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751437Ab1GTODk (ORCPT ); Wed, 20 Jul 2011 10:03:40 -0400 Date: Wed, 20 Jul 2011 16:03:35 +0200 From: Tejun Heo To: Pavel Emelyanov , Nathan Lynch , Oren Laadan , Daniel Lezcano , Serge Hallyn , Cyrill Gorcunov , Glauber Costa , Oleg Nesterov , Andrew Morton Cc: Linux Containers , linux-kernel@vger.kernel.org Subject: Re: [EXAMPLE CODE] Parasite thread injection using PTRACE_SEIZE and friends Message-ID: <20110720140335.GN3455@htj.dyndns.org> References: <20110720140037.GM3455@htj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110720140037.GM3455@htj.dyndns.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.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. Thanks. -- tejun