• Tycho Andersen's avatar
    seccomp: add a --no-seccomp option to disable dumping seccomp · a98014f3
    Tycho Andersen authored
    Sometimes we may want to use CRIU on older kernels which don't support
    dumping seccomp state where we don't actually care about the seccomp state.
    Of course this is unsafe, but it does allow for c/r of things using
    seccomp on these older kernels in some cases. When the task is in
    SECCOMP_MODE_STRICT or SECCOMP_MODE_FILTER with filters that block the
    syscalls criu's parasite code needs, the dump will still fail.
    
    Note that we disable seccomp by simply feigning that we are in mode 0. This
    is a little hacky, but avoids distributing ifs throughout the code and
    keeps them in this one place.
    Signed-off-by: 's avatarTycho Andersen <tycho.andersen@canonical.com>
    CC: Saied Kazemi <saied@google.com>
    Signed-off-by: 's avatarPavel Emelyanov <xemul@virtuozzo.com>
    a98014f3
Name
Last commit
Last update
..
.gitattributes Loading commit data...
.gitignore Loading commit data...
HOWTO.cross-compile Loading commit data...
Makefile Loading commit data...
asciidoc.conf Loading commit data...
criu.txt Loading commit data...