From: Adrian Reber <hidden> Date: 2020-07-15 14:51:13
This is v5 of the 'Introduce CAP_CHECKPOINT_RESTORE' patchset. The
changes to v4 are:
* split into more patches to have the introduction of
CAP_CHECKPOINT_RESTORE and the actual usage in different
patches
* reduce the /proc/self/exe patch to only be about
CAP_CHECKPOINT_RESTORE
Adrian Reber (5):
capabilities: Introduce CAP_CHECKPOINT_RESTORE
pid: use checkpoint_restore_ns_capable() for set_tid
pid_namespace: use checkpoint_restore_ns_capable() for ns_last_pid
proc: allow access in init userns for map_files with CAP_CHECKPOINT_RESTORE
selftests: add clone3() CAP_CHECKPOINT_RESTORE test
Nicolas Viennot (1):
prctl: Allow checkpoint/restore capable processes to change exe link
fs/proc/base.c | 8 +-
include/linux/capability.h | 6 +
include/uapi/linux/capability.h | 9 +-
kernel/pid.c | 2 +-
kernel/pid_namespace.c | 2 +-
kernel/sys.c | 12 +-
security/selinux/include/classmap.h | 5 +-
tools/testing/selftests/clone3/Makefile | 4 +-
.../clone3/clone3_cap_checkpoint_restore.c | 203 ++++++++++++++++++
9 files changed, 236 insertions(+), 15 deletions(-)
create mode 100644 tools/testing/selftests/clone3/clone3_cap_checkpoint_restore.c
base-commit: d31958b30ea3b7b6e522d6bf449427748ad45822
--
2.26.2
From: Adrian Reber <hidden> Date: 2020-07-15 14:51:23
This patch introduces CAP_CHECKPOINT_RESTORE, a new capability facilitating
checkpoint/restore for non-root users.
Over the last years, The CRIU (Checkpoint/Restore In Userspace) team has been
asked numerous times if it is possible to checkpoint/restore a process as
non-root. The answer usually was: 'almost'.
The main blocker to restore a process as non-root was to control the PID of the
restored process. This feature available via the clone3 system call, or via
/proc/sys/kernel/ns_last_pid is unfortunately guarded by CAP_SYS_ADMIN.
In the past two years, requests for non-root checkpoint/restore have increased
due to the following use cases:
* Checkpoint/Restore in an HPC environment in combination with a resource
manager distributing jobs where users are always running as non-root.
There is a desire to provide a way to checkpoint and restore long running
jobs.
* Container migration as non-root
* We have been in contact with JVM developers who are integrating
CRIU into a Java VM to decrease the startup time. These checkpoint/restore
applications are not meant to be running with CAP_SYS_ADMIN.
We have seen the following workarounds:
* Use a setuid wrapper around CRIU:
See https://github.com/FredHutch/slurm-examples/blob/master/checkpointer/lib/checkpointer/checkpointer-suid.c
* Use a setuid helper that writes to ns_last_pid.
Unfortunately, this helper delegation technique is impossible to use with
clone3, and is thus prone to races.
See https://github.com/twosigma/set_ns_last_pid
* Cycle through PIDs with fork() until the desired PID is reached:
This has been demonstrated to work with cycling rates of 100,000 PIDs/s
See https://github.com/twosigma/set_ns_last_pid
* Patch out the CAP_SYS_ADMIN check from the kernel
* Run the desired application in a new user and PID namespace to provide
a local CAP_SYS_ADMIN for controlling PIDs. This technique has limited use in
typical container environments (e.g., Kubernetes) as /proc is
typically protected with read-only layers (e.g., /proc/sys) for hardening
purposes. Read-only layers prevent additional /proc mounts (due to proc's
SB_I_USERNS_VISIBLE property), making the use of new PID namespaces limited as
certain applications need access to /proc matching their PID namespace.
The introduced capability allows to:
* Control PIDs when the current user is CAP_CHECKPOINT_RESTORE capable
for the corresponding PID namespace via ns_last_pid/clone3.
* Open files in /proc/pid/map_files when the current user is
CAP_CHECKPOINT_RESTORE capable in the root namespace, useful for recovering
files that are unreachable via the file system such as deleted files, or memfd
files.
See corresponding selftest for an example with clone3().
Signed-off-by: Adrian Reber <redacted>
Signed-off-by: Nicolas Viennot <redacted>
---
include/linux/capability.h | 6 ++++++
include/uapi/linux/capability.h | 9 ++++++++-
security/selinux/include/classmap.h | 5 +++--
3 files changed, 17 insertions(+), 3 deletions(-)
@@ -261,6 +261,12 @@ static inline bool bpf_capable(void)returncapable(CAP_BPF)||capable(CAP_SYS_ADMIN);}+staticinlineboolcheckpoint_restore_ns_capable(structuser_namespace*ns)+{+returnns_capable(ns,CAP_CHECKPOINT_RESTORE)||+ns_capable(ns,CAP_SYS_ADMIN);+}+/* audit system wants to get cap info from files as well */externintget_vfs_caps_from_disk(conststructdentry*dentry,structcpu_vfs_cap_data*cpu_caps);
From: Adrian Reber <hidden> Date: 2020-07-15 14:51:37
Use the newly introduced capability CAP_CHECKPOINT_RESTORE to allow
using clone3() with set_tid set.
Signed-off-by: Adrian Reber <redacted>
Signed-off-by: Nicolas Viennot <redacted>
---
kernel/pid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Adrian Reber <hidden> Date: 2020-07-15 14:53:08
From: Nicolas Viennot <redacted>
Allow CAP_CHECKPOINT_RESTORE capable users to change /proc/self/exe.
This commit also changes the permission error code from -EINVAL to
-EPERM for consistency with the rest of the prctl() syscall when
checking capabilities.
Signed-off-by: Nicolas Viennot <redacted>
Signed-off-by: Adrian Reber <redacted>
---
kernel/sys.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
From: Adrian Reber <hidden> Date: 2020-07-15 14:53:11
Opening files in /proc/pid/map_files when the current user is
CAP_CHECKPOINT_RESTORE capable in the root namespace is useful for
checkpointing and restoring to recover files that are unreachable via
the file system such as deleted files, or memfd files.
Signed-off-by: Adrian Reber <redacted>
Signed-off-by: Nicolas Viennot <redacted>
---
fs/proc/base.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
From: Adrian Reber <hidden> Date: 2020-07-15 14:53:21
This adds a test that changes its UID, uses capabilities to
get CAP_CHECKPOINT_RESTORE and uses clone3() with set_tid to
create a process with a given PID as non-root.
Signed-off-by: Adrian Reber <redacted>
Acked-by: Serge Hallyn <serge@hallyn.com>
---
tools/testing/selftests/clone3/Makefile | 4 +-
.../clone3/clone3_cap_checkpoint_restore.c | 203 ++++++++++++++++++
2 files changed, 206 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/clone3/clone3_cap_checkpoint_restore.c
@@ -0,0 +1,203 @@+// SPDX-License-Identifier: GPL-2.0++/*+*BasedonChristianBrauner'sclone3()example.+*Thesetestsareassumingtoberunninginthehost's+*PIDnamespace.+*/++/* capabilities related code based on selftests/bpf/test_verifier.c */++#define _GNU_SOURCE+#include<errno.h>+#include<linux/types.h>+#include<linux/sched.h>+#include<stdio.h>+#include<stdlib.h>+#include<stdbool.h>+#include<sys/capability.h>+#include<sys/prctl.h>+#include<sys/syscall.h>+#include<sys/types.h>+#include<sys/un.h>+#include<sys/wait.h>+#include<unistd.h>+#include<sched.h>++#include"../kselftest.h"+#include"clone3_selftests.h"++#ifndef MAX_PID_NS_LEVEL+#define MAX_PID_NS_LEVEL 32+#endif++staticvoidchild_exit(intret)+{+fflush(stdout);+fflush(stderr);+_exit(ret);+}++staticintcall_clone3_set_tid(pid_t*set_tid,size_tset_tid_size)+{+intstatus;+pid_tpid=-1;++structclone_argsargs={+.exit_signal=SIGCHLD,+.set_tid=ptr_to_u64(set_tid),+.set_tid_size=set_tid_size,+};++pid=sys_clone3(&args,sizeof(structclone_args));+if(pid<0){+ksft_print_msg("%s - Failed to create new process\n",+strerror(errno));+return-errno;+}++if(pid==0){+intret;+chartmp=0;++ksft_print_msg+("I am the child, my PID is %d (expected %d)\n",+getpid(),set_tid[0]);++if(set_tid[0]!=getpid())+child_exit(EXIT_FAILURE);+child_exit(EXIT_SUCCESS);+}++ksft_print_msg("I am the parent (%d). My child's pid is %d\n",+getpid(),pid);++if(waitpid(pid,&status,0)<0){+ksft_print_msg("Child returned %s\n",strerror(errno));+return-errno;+}++if(!WIFEXITED(status))+return-1;++returnWEXITSTATUS(status);+}++staticinttest_clone3_set_tid(pid_t*set_tid,+size_tset_tid_size,intexpected)+{+intret;++ksft_print_msg("[%d] Trying clone3() with CLONE_SET_TID to %d\n",+getpid(),set_tid[0]);+ret=call_clone3_set_tid(set_tid,set_tid_size);++ksft_print_msg+("[%d] clone3() with CLONE_SET_TID %d says :%d - expected %d\n",+getpid(),set_tid[0],ret,expected);+if(ret!=expected){+ksft_test_result_fail+("[%d] Result (%d) is different than expected (%d)\n",+getpid(),ret,expected);+return-1;+}+ksft_test_result_pass+("[%d] Result (%d) matches expectation (%d)\n",getpid(),ret,+expected);++return0;+}++structlibcap{+struct__user_cap_header_structhdr;+struct__user_cap_data_structdata[2];+};++staticintset_capability()+{+cap_value_tcap_values[]={CAP_SETUID,CAP_SETGID};+structlibcap*cap;+intret=-1;+cap_tcaps;++caps=cap_get_proc();+if(!caps){+perror("cap_get_proc");+return-1;+}++/* Drop all capabilities */+if(cap_clear(caps)){+perror("cap_clear");+gotoout;+}++cap_set_flag(caps,CAP_EFFECTIVE,2,cap_values,CAP_SET);+cap_set_flag(caps,CAP_PERMITTED,2,cap_values,CAP_SET);++cap=(structlibcap*)caps;++/* 40 -> CAP_CHECKPOINT_RESTORE */+cap->data[1].effective|=1<<(40-32);+cap->data[1].permitted|=1<<(40-32);++if(cap_set_proc(caps)){+perror("cap_set_proc");+gotoout;+}+ret=0;+out:+if(cap_free(caps))+perror("cap_free");+returnret;+}++intmain(intargc,char*argv[])+{+pid_tpid;+intstatus;+intret=0;+pid_tset_tid[1];+uid_tuid=getuid();++ksft_print_header();+test_clone3_supported();+ksft_set_plan(2);++if(uid!=0){+ksft_cnt.ksft_xskip=ksft_plan;+ksft_print_msg("Skipping all tests as non-root\n");+returnksft_exit_pass();+}++memset(&set_tid,0,sizeof(set_tid));++/* Find the current active PID */+pid=fork();+if(pid==0){+ksft_print_msg("Child has PID %d\n",getpid());+child_exit(EXIT_SUCCESS);+}+if(waitpid(pid,&status,0)<0)+ksft_exit_fail_msg("Waiting for child %d failed",pid);++/* After the child has finished, its PID should be free. */+set_tid[0]=pid;++if(set_capability())+ksft_test_result_fail+("Could not set CAP_CHECKPOINT_RESTORE\n");+prctl(PR_SET_KEEPCAPS,1,0,0,0);+/* This would fail without CAP_CHECKPOINT_RESTORE */+setgid(1000);+setuid(1000);+set_tid[0]=pid;+ret|=test_clone3_set_tid(set_tid,1,-EPERM);+if(set_capability())+ksft_test_result_fail+("Could not set CAP_CHECKPOINT_RESTORE\n");+/* This should work as we have CAP_CHECKPOINT_RESTORE as non-root */+ret|=test_clone3_set_tid(set_tid,1,0);++return!ret?ksft_exit_pass():ksft_exit_fail();+}
From: Christian Brauner <hidden> Date: 2020-07-15 15:07:22
On Wed, Jul 15, 2020 at 04:49:49PM +0200, Adrian Reber wrote:
This patch introduces CAP_CHECKPOINT_RESTORE, a new capability facilitating
checkpoint/restore for non-root users.
Over the last years, The CRIU (Checkpoint/Restore In Userspace) team has been
asked numerous times if it is possible to checkpoint/restore a process as
non-root. The answer usually was: 'almost'.
The main blocker to restore a process as non-root was to control the PID of the
restored process. This feature available via the clone3 system call, or via
/proc/sys/kernel/ns_last_pid is unfortunately guarded by CAP_SYS_ADMIN.
In the past two years, requests for non-root checkpoint/restore have increased
due to the following use cases:
* Checkpoint/Restore in an HPC environment in combination with a resource
manager distributing jobs where users are always running as non-root.
There is a desire to provide a way to checkpoint and restore long running
jobs.
* Container migration as non-root
* We have been in contact with JVM developers who are integrating
CRIU into a Java VM to decrease the startup time. These checkpoint/restore
applications are not meant to be running with CAP_SYS_ADMIN.
We have seen the following workarounds:
* Use a setuid wrapper around CRIU:
See https://github.com/FredHutch/slurm-examples/blob/master/checkpointer/lib/checkpointer/checkpointer-suid.c
* Use a setuid helper that writes to ns_last_pid.
Unfortunately, this helper delegation technique is impossible to use with
clone3, and is thus prone to races.
See https://github.com/twosigma/set_ns_last_pid
* Cycle through PIDs with fork() until the desired PID is reached:
This has been demonstrated to work with cycling rates of 100,000 PIDs/s
See https://github.com/twosigma/set_ns_last_pid
* Patch out the CAP_SYS_ADMIN check from the kernel
* Run the desired application in a new user and PID namespace to provide
a local CAP_SYS_ADMIN for controlling PIDs. This technique has limited use in
typical container environments (e.g., Kubernetes) as /proc is
typically protected with read-only layers (e.g., /proc/sys) for hardening
purposes. Read-only layers prevent additional /proc mounts (due to proc's
SB_I_USERNS_VISIBLE property), making the use of new PID namespaces limited as
certain applications need access to /proc matching their PID namespace.
The introduced capability allows to:
* Control PIDs when the current user is CAP_CHECKPOINT_RESTORE capable
for the corresponding PID namespace via ns_last_pid/clone3.
* Open files in /proc/pid/map_files when the current user is
CAP_CHECKPOINT_RESTORE capable in the root namespace, useful for recovering
files that are unreachable via the file system such as deleted files, or memfd
files.
See corresponding selftest for an example with clone3().
Signed-off-by: Adrian Reber <redacted>
Signed-off-by: Nicolas Viennot <redacted>
---
Thanks!
This looks good now.
Acked-by: Christian Brauner <redacted>
@@ -261,6 +261,12 @@ static inline bool bpf_capable(void)returncapable(CAP_BPF)||capable(CAP_SYS_ADMIN);}+staticinlineboolcheckpoint_restore_ns_capable(structuser_namespace*ns)+{+returnns_capable(ns,CAP_CHECKPOINT_RESTORE)||+ns_capable(ns,CAP_SYS_ADMIN);+}+/* audit system wants to get cap info from files as well */externintget_vfs_caps_from_disk(conststructdentry*dentry,structcpu_vfs_cap_data*cpu_caps);
From: Christian Brauner <hidden> Date: 2020-07-15 15:08:40
On Wed, Jul 15, 2020 at 04:49:50PM +0200, Adrian Reber wrote:
Use the newly introduced capability CAP_CHECKPOINT_RESTORE to allow
using clone3() with set_tid set.
Signed-off-by: Adrian Reber <redacted>
Signed-off-by: Nicolas Viennot <redacted>
---
Looks good!
Acked-by: Christian Brauner <redacted>
From: Christian Brauner <hidden> Date: 2020-07-15 15:09:02
On Wed, Jul 15, 2020 at 04:49:51PM +0200, Adrian Reber wrote:
Use the newly introduced capability CAP_CHECKPOINT_RESTORE to allow
writing to ns_last_pid.
Signed-off-by: Adrian Reber <redacted>
Signed-off-by: Nicolas Viennot <redacted>
---
From: Christian Brauner <hidden> Date: 2020-07-15 15:20:40
On Wed, Jul 15, 2020 at 04:49:53PM +0200, Adrian Reber wrote:
From: Nicolas Viennot <redacted>
Allow CAP_CHECKPOINT_RESTORE capable users to change /proc/self/exe.
This commit also changes the permission error code from -EINVAL to
-EPERM for consistency with the rest of the prctl() syscall when
checking capabilities.
I agree that EINVAL seems weird here but this is a potentially user
visible change. Might be nice to have the EINVAL->EPERM change be an
additional patch on top after this one so we can revert it in case it
breaks someone (unlikely though). I can split this out myself though so
no need to resend for that alone.
What I would also prefer is to have some history in the commit message
tbh. The reason is that when we started discussing that specific change
I had to hunt down the history of changing /proc/self/exe and had to
dig up and read through ancient threads on lore to come up with the
explanation why this is placed under a capability. The commit message
should then also mention that there are other ways to change the
/proc/self/exe link that don't require capabilities and that
/proc/self/exe itself is not something userspace should rely on for
security. Mainly so that in a few months/years we can read through that
commit message and go "Weird, but ok.". :)
But maybe I can just rewrite this myself so you don't have to go through
the trouble. This is really not pedantry it's just that it's a lot of
work digging up the reasons for a piece of code existing when it's
really not obvious. :)
Christian
quoted hunk
Signed-off-by: Nicolas Viennot <redacted>
Signed-off-by: Adrian Reber <redacted>
---
kernel/sys.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
From: Christian Brauner <hidden> Date: 2020-07-15 15:25:06
On Wed, Jul 15, 2020 at 04:49:54PM +0200, Adrian Reber wrote:
This adds a test that changes its UID, uses capabilities to
get CAP_CHECKPOINT_RESTORE and uses clone3() with set_tid to
create a process with a given PID as non-root.
Signed-off-by: Adrian Reber <redacted>
Acked-by: Serge Hallyn <serge@hallyn.com>
---
You need to add the new clone3_cap_checkpoint_restore binary to
.gitignore too. :)
And one more annoying request: can you port the selftests to use the
kselftest_harness.h infrastructure, please? It is way nicer to use, has
a more uniform feel, and generates better output. You can look at:
tools/testing/selftests/pidfd/pidfd_setns_test.c
tools/testing/selftests/seccomp/seccomp_bpf.c
and others for examples on how to use it.
Thanks!
Christian
@@ -0,0 +1,203 @@+// SPDX-License-Identifier: GPL-2.0++/*+*BasedonChristianBrauner'sclone3()example.+*Thesetestsareassumingtoberunninginthehost's+*PIDnamespace.+*/++/* capabilities related code based on selftests/bpf/test_verifier.c */++#define _GNU_SOURCE+#include<errno.h>+#include<linux/types.h>+#include<linux/sched.h>+#include<stdio.h>+#include<stdlib.h>+#include<stdbool.h>+#include<sys/capability.h>+#include<sys/prctl.h>+#include<sys/syscall.h>+#include<sys/types.h>+#include<sys/un.h>+#include<sys/wait.h>+#include<unistd.h>+#include<sched.h>++#include"../kselftest.h"+#include"clone3_selftests.h"++#ifndef MAX_PID_NS_LEVEL+#define MAX_PID_NS_LEVEL 32+#endif++staticvoidchild_exit(intret)+{+fflush(stdout);+fflush(stderr);+_exit(ret);+}++staticintcall_clone3_set_tid(pid_t*set_tid,size_tset_tid_size)+{+intstatus;+pid_tpid=-1;++structclone_argsargs={+.exit_signal=SIGCHLD,+.set_tid=ptr_to_u64(set_tid),+.set_tid_size=set_tid_size,+};++pid=sys_clone3(&args,sizeof(structclone_args));+if(pid<0){+ksft_print_msg("%s - Failed to create new process\n",+strerror(errno));+return-errno;+}++if(pid==0){+intret;+chartmp=0;++ksft_print_msg+("I am the child, my PID is %d (expected %d)\n",+getpid(),set_tid[0]);++if(set_tid[0]!=getpid())+child_exit(EXIT_FAILURE);+child_exit(EXIT_SUCCESS);+}++ksft_print_msg("I am the parent (%d). My child's pid is %d\n",+getpid(),pid);++if(waitpid(pid,&status,0)<0){+ksft_print_msg("Child returned %s\n",strerror(errno));+return-errno;+}++if(!WIFEXITED(status))+return-1;++returnWEXITSTATUS(status);+}++staticinttest_clone3_set_tid(pid_t*set_tid,+size_tset_tid_size,intexpected)+{+intret;++ksft_print_msg("[%d] Trying clone3() with CLONE_SET_TID to %d\n",+getpid(),set_tid[0]);+ret=call_clone3_set_tid(set_tid,set_tid_size);++ksft_print_msg+("[%d] clone3() with CLONE_SET_TID %d says :%d - expected %d\n",+getpid(),set_tid[0],ret,expected);+if(ret!=expected){+ksft_test_result_fail+("[%d] Result (%d) is different than expected (%d)\n",+getpid(),ret,expected);+return-1;+}+ksft_test_result_pass+("[%d] Result (%d) matches expectation (%d)\n",getpid(),ret,+expected);++return0;+}++structlibcap{+struct__user_cap_header_structhdr;+struct__user_cap_data_structdata[2];+};++staticintset_capability()+{+cap_value_tcap_values[]={CAP_SETUID,CAP_SETGID};+structlibcap*cap;+intret=-1;+cap_tcaps;++caps=cap_get_proc();+if(!caps){+perror("cap_get_proc");+return-1;+}++/* Drop all capabilities */+if(cap_clear(caps)){+perror("cap_clear");+gotoout;+}++cap_set_flag(caps,CAP_EFFECTIVE,2,cap_values,CAP_SET);+cap_set_flag(caps,CAP_PERMITTED,2,cap_values,CAP_SET);++cap=(structlibcap*)caps;++/* 40 -> CAP_CHECKPOINT_RESTORE */+cap->data[1].effective|=1<<(40-32);+cap->data[1].permitted|=1<<(40-32);++if(cap_set_proc(caps)){+perror("cap_set_proc");+gotoout;+}+ret=0;+out:+if(cap_free(caps))+perror("cap_free");+returnret;+}++intmain(intargc,char*argv[])+{+pid_tpid;+intstatus;+intret=0;+pid_tset_tid[1];+uid_tuid=getuid();++ksft_print_header();+test_clone3_supported();+ksft_set_plan(2);++if(uid!=0){+ksft_cnt.ksft_xskip=ksft_plan;+ksft_print_msg("Skipping all tests as non-root\n");+returnksft_exit_pass();+}++memset(&set_tid,0,sizeof(set_tid));++/* Find the current active PID */+pid=fork();+if(pid==0){+ksft_print_msg("Child has PID %d\n",getpid());+child_exit(EXIT_SUCCESS);+}+if(waitpid(pid,&status,0)<0)+ksft_exit_fail_msg("Waiting for child %d failed",pid);++/* After the child has finished, its PID should be free. */+set_tid[0]=pid;++if(set_capability())+ksft_test_result_fail+("Could not set CAP_CHECKPOINT_RESTORE\n");+prctl(PR_SET_KEEPCAPS,1,0,0,0);+/* This would fail without CAP_CHECKPOINT_RESTORE */+setgid(1000);+setuid(1000);+set_tid[0]=pid;+ret|=test_clone3_set_tid(set_tid,1,-EPERM);+if(set_capability())+ksft_test_result_fail+("Could not set CAP_CHECKPOINT_RESTORE\n");+/* This should work as we have CAP_CHECKPOINT_RESTORE as non-root */+ret|=test_clone3_set_tid(set_tid,1,0);++return!ret?ksft_exit_pass():ksft_exit_fail();+}
From: Nicolas Viennot <hidden> Date: 2020-07-15 15:50:04
On Wed, Jul 15, 2020 at 04:49:53PM +0200, Adrian Reber wrote:
quoted
From: Nicolas Viennot <redacted>
Allow CAP_CHECKPOINT_RESTORE capable users to change /proc/self/exe.
This commit also changes the permission error code from -EINVAL to
-EPERM for consistency with the rest of the prctl() syscall when
checking capabilities.
I agree that EINVAL seems weird here but this is a potentially user visible change. Might be nice to have the EINVAL->EPERM change be an additional patch on top after this one so we can revert it in case it breaks someone (unlikely though). I can split this out myself though so no need to resend for that alone.
What I would also prefer is to have some history in the commit message tbh. The reason is that when we started discussing that specific change I had to hunt down the history of changing /proc/self/exe and had to dig up and read through ancient threads on lore to come up with the explanation why this is placed under a capability. The commit message should then also mention that there are other ways to change the /proc/self/exe link that don't require capabilities and that /proc/self/exe itself is not something userspace should rely on for security. Mainly so that in a few months/years we can read through that commit message and go "Weird, but ok.". :)
But maybe I can just rewrite this myself so you don't have to go through the trouble. This is really not pedantry it's just that it's a lot of work digging up the reasons for a piece of code existing when it's really not obvious. :)
Hello Christian,
I agree.
Thank you for suggesting doing the work, but you've done plenty already. So we'll come back to you with:
1) A separate commit for EINVAL->EPERM
2) A full history of discussions in the commit message related to /proc/self/exe capability check
Thanks,
Nico
On Wed, Jul 15, 2020 at 04:49:52PM +0200, Adrian Reber wrote:
Opening files in /proc/pid/map_files when the current user is
CAP_CHECKPOINT_RESTORE capable in the root namespace is useful for
checkpointing and restoring to recover files that are unreachable via
the file system such as deleted files, or memfd files.
Signed-off-by: Adrian Reber <redacted>
Signed-off-by: Nicolas Viennot <redacted>
I still have a plan to make this code been usable without
capabilities requirements but due to lack of spare time
for deep investigation this won't happen anytime soon.
Thus the patch looks OK to me, fwiw
Reviewed-by: Cyrill Gorcunov <redacted>
From: Christian Brauner <hidden> Date: 2020-07-16 08:52:03
On Wed, Jul 15, 2020 at 04:49:52PM +0200, Adrian Reber wrote:
quoted hunk
Opening files in /proc/pid/map_files when the current user is
CAP_CHECKPOINT_RESTORE capable in the root namespace is useful for
checkpointing and restoring to recover files that are unreachable via
the file system such as deleted files, or memfd files.
Signed-off-by: Adrian Reber <redacted>
Signed-off-by: Nicolas Viennot <redacted>
---
fs/proc/base.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
So right now, when I'd do
git grep checkpoint_restore_ns_capable
I'd not hit that codepath which isn't great. So I'd suggest to use:
if (!checkpoint_restore_ns_capable(&init_user_ns))
at the end of the day, capable(<cap>) just calls
ns_capable(&init_user_ns, <cap>) anyway.
Thanks!
Christian
From: "Serge E. Hallyn" <serge@hallyn.com> Date: 2020-07-18 03:24:22
On Wed, Jul 15, 2020 at 04:49:48PM +0200, Adrian Reber wrote:
This is v5 of the 'Introduce CAP_CHECKPOINT_RESTORE' patchset. The
changes to v4 are:
* split into more patches to have the introduction of
CAP_CHECKPOINT_RESTORE and the actual usage in different
patches
* reduce the /proc/self/exe patch to only be about
CAP_CHECKPOINT_RESTORE
Adrian Reber (5):
capabilities: Introduce CAP_CHECKPOINT_RESTORE
pid: use checkpoint_restore_ns_capable() for set_tid
pid_namespace: use checkpoint_restore_ns_capable() for ns_last_pid
proc: allow access in init userns for map_files with CAP_CHECKPOINT_RESTORE
selftests: add clone3() CAP_CHECKPOINT_RESTORE test
Nicolas Viennot (1):
prctl: Allow checkpoint/restore capable processes to change exe link
(This is probably bad form, but) All
Reviewed-by: Serge Hallyn <serge@hallyn.com>
Assuming you changes patches 4 and 6 per Christian's suggestions,
I'd like to re-review those then.
From: Christian Brauner <hidden> Date: 2020-07-18 17:48:17
On Fri, Jul 17, 2020 at 10:24:16PM -0500, Serge Hallyn wrote:
On Wed, Jul 15, 2020 at 04:49:48PM +0200, Adrian Reber wrote:
quoted
This is v5 of the 'Introduce CAP_CHECKPOINT_RESTORE' patchset. The
changes to v4 are:
* split into more patches to have the introduction of
CAP_CHECKPOINT_RESTORE and the actual usage in different
patches
* reduce the /proc/self/exe patch to only be about
CAP_CHECKPOINT_RESTORE
Adrian Reber (5):
capabilities: Introduce CAP_CHECKPOINT_RESTORE
pid: use checkpoint_restore_ns_capable() for set_tid
pid_namespace: use checkpoint_restore_ns_capable() for ns_last_pid
proc: allow access in init userns for map_files with CAP_CHECKPOINT_RESTORE
selftests: add clone3() CAP_CHECKPOINT_RESTORE test
Nicolas Viennot (1):
prctl: Allow checkpoint/restore capable processes to change exe link
(This is probably bad form, but) All
Reviewed-by: Serge Hallyn <serge@hallyn.com>
Assuming you changes patches 4 and 6 per Christian's suggestions,
I'd like to re-review those then.
Thanks, once Adrian has reposted the changes and you agree with them as
well, I'll pick them up though I might end up pushing this into the next
merge window...
Christian