2,257
edits
Changes
no edit summary
* Mentor: Adrian Reber <areber@redhat.com>
* Mentor: Adrian Reber <areber@redhat.com>
* Suggested by: Adrian Reber <areber@redhat.com>
* Suggested by: Adrian Reber <areber@redhat.com>
=== Restrict checks for open/mmaped files ===
'''Summary:''' Make sure the file opened (for fd or mapping) at restore is "the same" as it was on dump
CRIU doesn't carry files contents (except for ghost ones) into images. Thus on dump it saves some "meta" for file to validate it's "the same" on restore. Currently this meta includes only the file size. The task is to add some cookie value that's somehow affected by file's contents. This is primarily needed to reduce the possibility to restore with wrong libraries.
'''Links:'''
* https://www.criu.org/Category:Files
* https://en.wikipedia.org/wiki/File_verification
'''Details:'''
* Skill level: beginner
* Language: C
* Mentor: Pavel Emelyanov <xemul@openvz.org>
* Suggested by: Pavel Emelyanov <xemul@openvz.org>
[[Category:GSoC]]
[[Category:GSoC]]
[[Category:Development]]
[[Category:Development]]