criu/protobuf/ghost-file.proto

message ghost_file_entry {
	required uint32		uid		= 1;
	required uint32		gid		= 2;
	required uint32		mode		= 3;

	optional uint32		dev		= 4;
	optional uint64		ino		= 5;
	optional uint32		rdev		= 6;
}
protobuf: Use GhostFileEntry instead of struct ghost_file_entry Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2012-07-17 07:17:51 +04:00			`message ghost_file_entry {`
			`required uint32 uid = 1;`
			`required uint32 gid = 2;`
			`required uint32 mode = 3;`
ghost-files: Save device and inode in image Because we need to lookup for ghost files from inotify system where we only have device/inode as a key, we save dev/ino in ghost image entry. Note we use in-kernel format for device to be consistent with inotify and mount related code base. Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2012-12-06 11:11:10 +04:00
			`optional uint32 dev = 4;`
			`optional uint64 ino = 5;`
files: Support ghost devices When we have opened and unlinked chr or blk device, we shouls also take care of their rdev value. Thus -- new field in image and some new steps on dump and restore. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2014-07-02 13:32:47 +04:00			`optional uint32 rdev = 6;`
protobuf: Use GhostFileEntry instead of struct ghost_file_entry Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2012-07-17 07:17:51 +04:00			`}`