linux-kernel - Re: [PATCH 05/10] Core checkpoint/restart support code

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: <20110403190324.GD15044@hallyn.com>
Date:	Sun, 3 Apr 2011 14:03:24 -0500
From:	"Serge E. Hallyn" <serge@...lyn.com>
To:	ntl@...ox.com
Cc:	linux-kernel@...r.kernel.org,
	containers@...ts.linux-foundation.org,
	Oren Laadan <orenl@...columbia.edu>,
	Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [PATCH 05/10] Core checkpoint/restart support code

Quoting ntl@...ox.com (ntl@...ox.com):
> Only a pid namespace init task - the child process produced by a call
> to clone(2) with CLONE_NEWPID - is allowed to call these.  The state

So you make this useful for your cases by only using this with
application containers - created using lxc-execute, or, more precisely,
using lxc-init as the container's init.  So a container running a stock
distro can't be checkpointed.

Is this just to keep the patch simple for now, or is there some reason
to keep this limitation in place?

-serge
--
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/