Postulates - Revision history

Kir: some reformatting / rephrasing, added see also

2016-09-02T18:31:22Z

some reformatting / rephrasing, added see also

2016-04-19T10:45:32Z

2013-10-02T19:23:26Z

2013-09-27T10:21:56Z

2013-04-08T02:12:26Z

2013-02-22T20:28:13Z

english ;)

2013-01-06T10:47:28Z

Created page with "* All shared resources should be restored by a task with minimal PID for avoiding deadlocks."

New page

* All shared resources should be restored by a task with minimal PID for avoiding deadlocks.

@@ Line 1: / Line 1: @@
-* All shared resources must be restored by the task with the least PID to avoid deadlocks.
+Here are a few principles that must be taken into account while developing CRIU.
-* No operations with file paths in restorer blob -- task has restored it's fs (cwd and root) and may see different tree.
-* In "dump" code any fork()+exec() should be done using the cr_system() helper not to interfere with victim task tracing.
+* All shared resources must be restored by the task with the lowest PID among the group to avoid deadlocks.
-* To keep backward compatibility on protobuf image files, follow those rules (short notes from [https://developers.google.com/protocol-buffers/docs/proto#updating protobuf messages updating guide]):
+* No operations with file paths in restorer blob — task has restored its fs (cwd and root) and may see a different tree.
-** Don't change the numeric tags for any existing fields.
+* In dumping code, any fork()+exec() should be done using the cr_system() helper to avoid interfering with victim task tracing.
-** Any new fields that you add should be optional or repeated.
-** Non-required fields can be removed, as long as the tag number is not used again in your updated message type.
+== Protobuf images compatibility ==
 [[Category:Development]]

@@ Line 2: / Line 2: @@
 * No operations with file paths in restorer blob -- task has restored it's fs (cwd and root) and may see different tree.
 * In "dump" code any fork()+exec() should be done using the cr_system() helper not to interfere with victim task tracing.
 [[Category:Development]]

@@ Line 1: / Line 1: @@
 * All shared resources must be restored by the task with the least PID to avoid deadlocks.
 * No operations with file paths in restorer blob -- task has restored it's fs (cwd and root) and may see different tree.
 [[Category:Development]]

← Older revision		Revision as of 10:21, 27 September 2013
Line 1:		Line 1:
	* All shared resources must be restored by the task with the least PID to avoid deadlocks.		* All shared resources must be restored by the task with the least PID to avoid deadlocks.
		+	* No operations with file paths in restorer blob -- task has restored it's fs (cwd and root) and may see different tree.

	[[Category:Development]]		[[Category:Development]]

← Older revision		Revision as of 02:12, 8 April 2013
Line 1:		Line 1:
	* All shared resources must be restored by the task with the least PID to avoid deadlocks.		* All shared resources must be restored by the task with the least PID to avoid deadlocks.
		+
		+	[[Category:Development]]

← Older revision		Revision as of 20:28, 22 February 2013
Line 1:		Line 1:
−	* All shared resources ~~should~~ be restored by a task with ~~minimal~~ PID ~~for avoiding~~ deadlocks.	+	* All shared resources must be restored by the task with the least PID to avoid deadlocks.