2,257
edits
Changes
Jump to navigation
Jump to search
Line 19:
Line 19: + + + +
→How file can lose it's path
There's a third possibility for a file not to have a visible name. But this is another story, that has nothing to do with dumping opened files, this it's described in a [[How to open a file without open system call|another article]].
There's a third possibility for a file not to have a visible name. But this is another story, that has nothing to do with dumping opened files, this it's described in a [[How to open a file without open system call|another article]].
=== Overmounted files ===
If a task opens a file and then a new mountpoint appears on any part of its path, the original file's path may become non existing or point to different file. In Linux there's no way to open a file by a name looking ''under'' certain mount points, but there's the openat() call which may look up a file starting from arbitrary point which, in turn, can be over-mounted too.
== What CRIU does about it ==
== What CRIU does about it ==