-
Notifications
You must be signed in to change notification settings - Fork 584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Diagnose capability changes if migrating between kernels of different cap_last_cap. #2200
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## criu-dev #2200 +/- ##
============================================
- Coverage 70.35% 70.30% -0.06%
============================================
Files 133 132 -1
Lines 34001 33995 -6
============================================
- Hits 23923 23900 -23
- Misses 10078 10095 +17
☔ View full report in Codecov by Sentry. |
0f83a62
to
9f323ad
Compare
nit: pls remove these Change-Id tags. |
dd3691d
to
17cd778
Compare
021db4e
to
eef1dda
Compare
…els. When restoring on a kernel that has different number of supported capabilities than checkpoint one, check that the extra caps are unset. There are two directions to consider: 1) dump.cap_last_cap > restore.cap_last_cap - restoring might reduce the processes' capabilities if restored kernel doesn't support checkpointed caps. Warn. 2) dump.cap_last_cap < restore.cap_last_cap - restoring will fill the extra caps with zeroes. No changes. Note: `last_cap` might change without affecting `n_words`. Signed-off-by: Michał Mirosław <[email protected]>
Merged. Thanks |
Log when trying to restore capabilities unknown to the kernel.