Self dump - Revision history

Xemul at 13:50, 18 August 2017

2017-08-18T13:50:05Z

Xemul at 19:51, 10 March 2015

2015-03-10T19:51:43Z

Efiop at 17:30, 22 September 2013

2013-09-22T17:30:14Z

Xemul: Added potential security hole

2013-07-09T12:38:35Z

Added potential security hole

Xemul: /* Solution */

2013-07-09T12:36:42Z

Solution

Xemul: Fixed page description

2013-07-09T12:34:44Z

Fixed page description

Xemul: Created page with "This is an application may dump itself using CRIU software. == Difficulties == First of all, CRIU still requires root privileges to run. This is because the kernel APIs it u..."

2013-07-09T12:33:55Z

Created page with "This is an application may dump itself using CRIU software. == Difficulties == First of all, CRIU still requires root privileges to run. This is because the kernel APIs it u..."

New page

This is an application may dump itself using CRIU software.

== Difficulties ==

First of all, CRIU still requires root privileges to run. This is because the kernel APIs it uses are partly restricted to this. The situation will probably change in the future, but it's not one-day issue.

Second thing, is that if CRIU is spawned from or somehow linked into a program, that would like to do self-checkpoint, CRIU will have to tell resources of this application from those owned by CRIU itself. This task is complex and probably this is how CRIU will do stuff in the future.

== Solution ==

Thus, the solution is -- CRIU service, that is requested to dump a process(es). The self-dump request should look like this (it's not yet implemented):

* a CRIU daemon is launched in the background listening to connections to unix socket
* an application, that wants to checkpoint itself opens the connection and asks for it
* CRIU service spawns a process, that executes regular dump
* while dumping the connection is closed by CRIU, so application may read() the socket to wait for dump end

== Details ==

Some things to keep in mind

# Call to connect() should be wrapped into a library function. It's not nice to give raw access to this socket, as the communication protocol is prone to change and it's not nice to keep it backward-compatible.
# Application should somehow pass arguments to the CRIU service. At least -- the directory where to put images to. If wrapped into a library call, these args should be declared as a structure in memory, whose contents is then encoded into a stream. Requirement "service version == library version" will help not to keep this protocol compatible.
# Paths are better to be transferred as opened files (SCM_CREDS)
# Waiting for socket to get closed by CRIU is good way to wait for checkpoint to complete. In this case CRIU should close the socket after freeze, but before dump to properly dump the half-closed connection in the program.

← Older revision		Revision as of 13:50, 18 August 2017
Line 29:		Line 29:
	# What if applications runs another one and asks to dump itself with kids? In this case the app in question would be able to investigate its sub-task's guts, which would otherwise be impossible.		# What if applications runs another one and asks to dump itself with kids? In this case the app in question would be able to investigate its sub-task's guts, which would otherwise be impossible.

−	[[Category: ~~Development~~]]	+	[[Category: Plans]]

← Older revision		Revision as of 19:51, 10 March 2015
Line 28:		Line 28:
	# Waiting for socket to get closed by CRIU is good way to wait for checkpoint to complete. In this case CRIU should close the socket after freeze, but before dump to properly dump the half-closed connection in the program.		# Waiting for socket to get closed by CRIU is good way to wait for checkpoint to complete. In this case CRIU should close the socket after freeze, but before dump to properly dump the half-closed connection in the program.
	# What if applications runs another one and asks to dump itself with kids? In this case the app in question would be able to investigate its sub-task's guts, which would otherwise be impossible.		# What if applications runs another one and asks to dump itself with kids? In this case the app in question would be able to investigate its sub-task's guts, which would otherwise be impossible.
		+
		+	[[Category: Development]]

← Older revision		Revision as of 17:30, 22 September 2013
Line 1:		Line 1:
		+	'''NOTE: Information on this page is outdated. Features described here are implemented in [[RPC]].'''
		+
	Applications want to dump themselves using CRIU software. This page describes how this should be implemented in CRIU.		Applications want to dump themselves using CRIU software. This page describes how this should be implemented in CRIU.

← Older revision		Revision as of 12:38, 9 July 2013
Line 25:		Line 25:
	# Paths are better to be transferred as opened files (SCM_CREDS)		# Paths are better to be transferred as opened files (SCM_CREDS)
	# Waiting for socket to get closed by CRIU is good way to wait for checkpoint to complete. In this case CRIU should close the socket after freeze, but before dump to properly dump the half-closed connection in the program.		# Waiting for socket to get closed by CRIU is good way to wait for checkpoint to complete. In this case CRIU should close the socket after freeze, but before dump to properly dump the half-closed connection in the program.
		+	# What if applications runs another one and asks to dump itself with kids? In this case the app in question would be able to investigate its sub-task's guts, which would otherwise be impossible.

← Older revision		Revision as of 12:34, 9 July 2013
Line 1:		Line 1:
−	~~This is an application may~~ dump ~~itself~~ using CRIU software.	+	Applications want to dump themselves using CRIU software. This page describes how this should be implemented in CRIU.

	== Difficulties ==		== Difficulties ==

@@ Line 13: / Line 13: @@
 * a CRIU daemon is launched in the background listening to connections to unix socket
 * an application, that wants to checkpoint itself opens the connection and asks for it
 * CRIU service spawns a process, that executes regular dump
 * while dumping the connection is closed by CRIU, so application may read() the socket to wait for dump end