> CRIU's restoring tasks enter the VE before it runs, so they stay
> VD_PTRACE_COREDUMP. A container binary run during the restore, such as
> the tee that post-restore runs via vzctl exec3, can open their
> /proc/<pid>/fd and take CRIU's log, its /proc fd and the transport
> socket.
> 
> Mark a task the host sends into a starting VE as VD_VE_SETUP_TASK.
> Fork keeps the mark and exec drops it. While the VE is pseudosuper, such
> a task dumps no core and is reachable only from another setup task of
> the VE, so CRIU's tasks still reach each other and what they exec does
> not. Once pseudosuper is cleared the mark counts as VD_PTRACE_COREDUMP,
> so the restored processes become ordinary ones.
> 
> Feature: trace: prohibit tracing sensitive tasks from CT
> https://virtuozzo.atlassian.net/browse/VSTOR-151265
> Signed-off-by: Mirian Shilakadze <[email protected]>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review ยท 
https://sashiko.vzint.dev/#/patchset/[email protected]?part=3


_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel

Reply via email to