kcmp.2: Since Linux 5.12, kcmp() availability is unconditional

kcmp() is no longer dependent on CONFIG_CHECKPOINT_RESTORE.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2021-03-02 13:16:38 +01:00
parent efbcc10934
commit b007f233f5
1 changed files with 7 additions and 5 deletions

View File

@ -306,14 +306,16 @@ is Linux-specific and should not be used in programs intended to be portable.
Glibc does not provide a wrapper for this system call; call it using
.BR syscall (2).
.PP
This system call is available only if the kernel was configured with
.BR CONFIG_CHECKPOINT_RESTORE .
The main use of the system call is for the
Before Linux 5.12,
this system call is available only if the kernel is configured with
.BR CONFIG_CHECKPOINT_RESTORE ,
since the original pupose the system call was for the
checkpoint/restore in user space (CRIU) feature.
The alternative to this system call would have been to expose suitable
(The alternative to this system call would have been to expose suitable
process information via the
.BR proc (5)
filesystem; this was deemed to be unsuitable for security reasons.
filesystem; this was deemed to be unsuitable for security reasons.)
Since Linux 5.12, this system call is made available unconditionally.
.PP
See
.BR clone (2)