Difference between revisions of "Pidfd store"
(Created page with "Pidfd store increases the reliability of pid reuse detection during pre-dumps/dumps using task pidfd instead of task creation time. It is only supported for RPC and the C lib...") |
(No difference)
|
Latest revision as of 10:41, 24 June 2021
Pidfd store increases the reliability of pid reuse detection during pre-dumps/dumps using task pidfd instead of task creation time.
It is only supported for RPC and the C library.
Usage[edit]
A connectionless unix socket is passed to CRIU during each pre-dump/dump through
the RPC option pidfd_store_sk or criu_set_pidfd_store_sk routine in the the library.
NOTE: This is targeted at migration tools like P.Haul, because the passed socket must be kept alive throughout all pre-dump/dump iterations.
Feature check[edit]
This feature requires pidfd_open and pidfd_getfd syscalls.
Support could be checked with:
- CLI:
criu check --feature pidfd_store. - RPC:
CRIU_REQ_TYPE__FEATURE_CHECKand setpidfd_storeto true in the "features" field of the request
How it works[edit]
The pidfd_store_sk is used as a queue for task pidfds. CRIU sends tasks pidfds to this socket and receives them in the next pre-dump/dump iteration. Those pidfds could then be used to check whether the task is still alive, otherwise it is a case of pid reuse and CRIU should make a full page dump.