lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111216160556.GB31770@google.com>
Date:	Fri, 16 Dec 2011 08:05:56 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Andrew Vagin <avagin@...nvz.org>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Roland McGrath <roland@...hat.com>,
	Oleg Nesterov <oleg@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Cyrill Gorcunov <gorcunov@...nvz.org>,
	Pavel Emelyanov <xemul@...allels.com>
Subject: Re: [PATCH 0/2] ptrace: add ability to attach a file descriptor to
 another process

Hello,

On Fri, Dec 16, 2011 at 01:46:21PM +0300, Andrew Vagin wrote:
> We need this functionality for checkpointing processes.  Now some parts
> are dumped with help PTRACE_SEIZE.  Parasite code is injected to process
> and it collects information.  This code should save data to somewhere.
> I want to suggest a scheme, when a dumper creates file descriptor and
> attaches it to a target process, then execute parasite code, which closes
> this descriptor at the end.
> 
> We can't create unix sockets or open files, because a process may
> be in another namespaces.

I really dislike this.  This doesn't belong in ptrace at all.  With
parasite, you have full control of the process, there gotta be some
other way to talk back.  Can't you create a management process w/ open
UNIX socket when spawning a namespace?  If that doesn't work, wouldn't
letting it dump to filesystem and retrieving it afterwards work?

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ