containers with inotify not in hardcoded locations can't be checkpointed
Bug #1575741 reported by
Tycho Andersen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| criu (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Right now CRIU uses a hardcoded list of common locations to place inotify hooks in order to figure out a reverse mapping between inode:path so it can restore the inotify hooks. We should support inotify at all locations. This probably requires kernel patches as well as userspace ones.
Revision history for this message
| Tycho Andersen (tycho-s) wrote | #1 |
| Changed in criu (Ubuntu): | |
| status: | New → Fix Committed |
| Changed in criu (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've committed a fix upstream that fixes this for filesystems that preserve inodes across moves (ZFS, BTRFS). I'm marking this as fix committed for now since we're encouraging people to use ZFS. If we move to a different filesystem, we'll need to revisit how we do this.