Difference between revisions of "CLI/opt/--allow-uprobes"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
| − | The <code>--allow-uprobes</code> command-line option allows CRIU to checkpoint and restore processes that have (or once had) | + | The <code>--allow-uprobes</code> command-line option allows CRIU to checkpoint and restore processes that have (or once had) a kernel-created uprobes VMA (user-space probes virtual memory area). Since this VMA persists even after the probe is removed, CRIU cannot safely infer the probe state at checkpoint time without this option. |
{{Note|If a checkpoint has been created with <code>--allow-uprobes</code>, this option '''must''' be specified during restore and any relevant uprobes '''must''' remain active. This option does not create or manage uprobes; it only instructs CRIU to accept the presence of the corresponding VMAs.}} | {{Note|If a checkpoint has been created with <code>--allow-uprobes</code>, this option '''must''' be specified during restore and any relevant uprobes '''must''' remain active. This option does not create or manage uprobes; it only instructs CRIU to accept the presence of the corresponding VMAs.}} | ||
Revision as of 12:42, 7 October 2025
The --allow-uprobes command-line option allows CRIU to checkpoint and restore processes that have (or once had) a kernel-created uprobes VMA (user-space probes virtual memory area). Since this VMA persists even after the probe is removed, CRIU cannot safely infer the probe state at checkpoint time without this option.
|
Note: If a checkpoint has been created with --allow-uprobes, this option must be specified during restore and any relevant uprobes must remain active. This option does not create or manage uprobes; it only instructs CRIU to accept the presence of the corresponding VMAs.
|