Difference between revisions of "Postulates"

From CRIU
Jump to navigation Jump to search
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.
 
* 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.
 
* In "dump" code any fork()+exec() should be done using the cr_system() helper not to interfere with victim task tracing.
 +
* 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]):
 +
** Don't change the numeric tags for any existing fields.
 +
** 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.
  
 
[[Category:Development]]
 
[[Category:Development]]

Revision as of 10:45, 19 April 2016

  • 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.
  • In "dump" code any fork()+exec() should be done using the cr_system() helper not to interfere with victim task tracing.
  • To keep backward compatibility on protobuf image files, follow those rules (short notes from protobuf messages updating guide):
    • Don't change the numeric tags for any existing fields.
    • 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.