nsfs: replace proc_ns_fget() with proc_ns_fdget()
Subsystems (7)
RFC PATCH v3 1/2 nsfs: replace proc_ns_fget() with proc_ns_fdget()
New helper function returns pointer to struct ns_common, can check namespace type and uses struct fd for returning file reference:
this saves couple atomic operations for single-threaded applications.
--- fs/nsfs.c | 20 +++++++++++++------- include/linux/proc_ns.h | 4 +++- kernel/nsproxy.c | 15 +++++---------- net/core/net_namespace.c | 18 ++++++------------ 4 files changed, 27 insertions(+), 30 deletions(-)
fs/nsfs.c +13 -7
@@ -119,21 +119,27 @@ int ns_get_name(char *buf, size_t size, struct task_struct *task,return res; } -struct file *proc_ns_fget (int fd) +struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref) { -struct file *file; +struct ns_common *ns; +struct fd f; - file =fget (fd); -if (!file) + f =fdget (fd); +if (!f.file)return ERR_PTR (-EBADF ); -if (file->f_op != &ns_file_operations) +if (f.file->f_op != &ns_file_operations) + goto out_invalid; + + ns =get_proc_ns (file_inode (f.file)); +if (nstype && (ns->ops->type != nstype)) goto out_invalid; -return file; + *fd_ref = f; +return ns; out_invalid: -fput (file); +fdput (f);return ERR_PTR (-EINVAL ); }
include/linux/proc_ns.h +3 -1
@@ -9,6 +9,7 @@struct pid_namespace ;struct nsproxy ;struct path ; +struct fd ;struct proc_ns_operations {const char *name;
@@ -65,7 +66,8 @@ static inline int ns_alloc_inum(struct ns_common *ns)#define ns_free_inum (ns) proc_free_inum((ns)->inum) -extern struct file *proc_ns_fget (int fd); +extern struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref); +#define get_proc_ns (inode) ((struct ns_common *)(inode)->i_private)extern void *ns_get_path (struct path *path,struct task_struct *task,const struct proc_ns_operations *ns_ops);
kernel/nsproxy.c +5 -10
@@ -222,18 +222,13 @@ SYSCALL_DEFINE2(setns, int, fd, int, nstype) {struct task_struct *tsk = current;struct nsproxy *new_nsproxy; -struct file *file; +struct fd fd_ref;struct ns_common *ns;int err; - file =proc_ns_fget (fd); -if (IS_ERR (file)) -return PTR_ERR (file); - - err = -EINVAL ; - ns =get_proc_ns (file_inode (file)); -if (nstype && (ns->ops->type != nstype)) - goto out; + ns =proc_ns_fdget (fd, nstype, &fd_ref); +if (IS_ERR (ns)) +return PTR_ERR (ns); new_nsproxy =create_new_namespaces (0 , tsk,current_user_ns (), tsk->fs);if (IS_ERR (new_nsproxy)) {
@@ -248,7 +243,7 @@ SYSCALL_DEFINE2(setns, int, fd, int, nstype) }switch_task_namespaces (tsk, new_nsproxy); out: -fput (file); +fdput (fd_ref);return err; }
net/core/net_namespace.c +6 -12
@@ -465,21 +465,15 @@ EXPORT_SYMBOL_GPL(__put_net);struct net *get_net_ns_by_fd (int fd) { -struct file *file;struct ns_common *ns; +struct fd fd_ref;struct net *net; - file =proc_ns_fget (fd); -if (IS_ERR (file)) -return ERR_CAST (file); - - ns =get_proc_ns (file_inode (file)); -if (ns->ops == &netns_operations) - net = get_net(container_of(ns, struct net, ns)); -else - net =ERR_PTR (-EINVAL ); - -fput (file); + ns =proc_ns_fdget (fd,CLONE_NEWNET , &fd_ref); +if (IS_ERR (ns)) +return ERR_CAST (ns); + net = get_net(container_of(ns, struct net, ns)); +fdput (fd_ref);return net; }
RFC PATCH v3 2/2 pidns: introduce syscall getvpid
pid_t getvpid(pid_t pid, int source, int target);
This syscall converts pid from source pid-namespace into pid visible in target pid-namespace. If pid is unreachable from target namespace then getvpid() returns zero.
Namespaces are defined by file descriptors pointing to entries in proc (/proc/[pid]/ns/pid). If argument is negative then current pid namespace is used.
If pid is negative then getvpid() returns pid of parent task for -pid.
Possible error codes:
ESRCH - task not found EBADF - closed file descriptor EINVAL - not pid-namespace file descriptor
Such conversion is required for interaction between processes from different pid-namespaces. For example system service at host system who provide access to restricted set of privileged operations for clients from containers have to convert pids back and forward.
Recent kernels expose virtual pids in /proc/[pid]/status:NSpid, but this interface works only in one way and even that is non-trivial.
Other option is passing pids with credentials via unix socket, but this solution requires a lot of preparation and CAP_SYS_ADMIN for sending arbitrary pids.
This syscall works in both directions, it's fast and simple.
Examples:
getvpid(pid, ns, -1) - get pid in our pid namespace getvpid(pid, -1, ns) - get pid in container getvpid(pid, -1, ns) > 0 - is pid is reachable from container? getvpid(1, ns1, ns2) > 0 - is ns1 inside ns2? getvpid(1, ns1, ns2) == 0 - is ns1 outside ns2? getvpid(1, ns, -1) - get init task of pid-namespace getvpid(-1, ns, -1) - get reaper of init task in parent pid-namespace getvpid(-pid, -1, -1) - get ppid by pid
--
v1: https://lkml.org/lkml/2015/9/15/411
v2: https://lkml.org/lkml/2015/9/24/278
v3:
* use proc_ns_fdget()
* update description
* rebase to next-20150925
* fix conflict with mlock2
--- arch/x86/entry/syscalls/syscall_32.tbl | 1 + arch/x86/entry/syscalls/syscall_64.tbl | 1 + include/linux/syscalls.h | 1 + include/uapi/asm-generic/unistd.h | 4 ++- kernel/sys.c | 51 ++++++++++++++++++++++++++++++++ 5 files changed, 57 insertions(+), 1 deletion(-)
arch/x86/entry/syscalls/syscall_32.tbl +1 -0
@@ -383,3 +383,4 @@ 374 i386 userfaultfd sys_userfaultfd 375 i386 membarrier sys_membarrier 376 i386 mlock2 sys_mlock2 +377 i386 getvpid sys_getvpid
arch/x86/entry/syscalls/syscall_64.tbl +1 -0
@@ -332,6 +332,7 @@ 323 common userfaultfd sys_userfaultfd 324 common membarrier sys_membarrier 325 common mlock2 sys_mlock2 +326 common getvpid sys_getvpid # # x32-specific system call numbers start at 512 to avoid cache impact
include/linux/syscalls.h +1 -0
@@ -222,6 +222,7 @@ asmlinkage long sys_nanosleep(struct timespec __user *rqtp, struct timespec __usasmlinkage long sys_alarm (unsigned int seconds);asmlinkage long sys_getpid (void );asmlinkage long sys_getppid (void ); +asmlinkage long sys_getvpid (pid_t pid,int source,int target);asmlinkage long sys_getuid (void );asmlinkage long sys_geteuid (void );asmlinkage long sys_getgid (void );
include/uapi/asm-generic/unistd.h +3 -1
@@ -715,9 +715,11 @@ __SYSCALL(__NR_userfaultfd, sys_userfaultfd) __SYSCALL(__NR_membarrier, sys_membarrier)#define __NR_mlock2 284 __SYSCALL(__NR_mlock2, sys_mlock2) +#define __NR_mlock2 285 +__SYSCALL(__NR_getvpid, sys_getvpid)#undef __NR_syscalls -#define __NR_syscalls 285 +#define __NR_syscalls 286/* * All syscalls below here should go away really,
kernel/sys.c +51 -0
63 lines not on this page · raw message
cover ns: introduce proc_get_ns_by_fd()
In reply to Konstantin KhlebnikovQuoted 20 lines · Konstantin Khlebnikov
fs/nsfs.c +10
-4+struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref) { -struct file *file; +struct ns_common *ns; +struct fd f; - file =fget (fd); -if (!file) + f =fdget (fd); +if (!f.file)return ERR_PTR (-EBADF ); -if (file->f_op != &ns_file_operations) +if (f.file->f_op != &ns_file_operations) + goto out_invalid; + + ns =get_proc_ns (file_inode (f.file)); +if (nstype && (ns->ops->type != nstype)) goto out_invalid;
fs/nsfs.c int ns_get_name(char *buf, size_t size, struct task_struct *task, · line 144
Quoted 10 lines
fs/nsfs.c +3
-2-return file; + *fd_ref = f; +return ns; out_invalid: -fput (file); +fdput (f);return ERR_PTR (-EINVAL ); }
Well yes, fdget() makes sense but this is minor.
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your sys_getvpid() can just use proc_get_ns_by_fd(fd, CLONE_NEWPID) and put_pid_ns().
Eric, what do you think?
See also "TODO" in the changelog.
Oleg.
PATCH 1/1 ns: introduce proc_get_ns_by_fd()
Introduce proc_get_ns_by_fd() so that get_net_ns_by_fd() becomes one-liner. It will have another CLONE_NEWPID user soon.
TODO: proc_get_ns_by_fd() can share some code with proc_ns_fget().
--- fs/nsfs.c | 24 ++++++++++++++++++++++++ include/linux/proc_ns.h | 3 +++ kernel/pid_namespace.c | 6 ++++++ net/core/net_namespace.c | 23 +++++++---------------- 4 files changed, 40 insertions(+), 16 deletions(-)
fs/nsfs.c +24 -0
@@ -136,6 +136,30 @@ out_invalid:return ERR_PTR (-EINVAL ); } +void *proc_get_ns_by_fd (int fd,int type) +{ +struct fd f; +struct ns_common *ns; +void *ret; + + f =fdget (fd); +if (!f.file) +return ERR_PTR (-EBADF ); + + ret =ERR_PTR (-EINVAL ); +if (f.file->f_op != &ns_file_operations) + goto put; + + ns =get_proc_ns (file_inode (f.file)); +if (ns->ops->type != type || !ns->ops->get_type) + goto put; + + ret = ns->ops->get_type (ns); +put: +fdput (f); +return ret; +} +static const struct super_operations nsfs_ops = { .statfs = simple_statfs, .evict_inode = nsfs_evict,
include/linux/proc_ns.h +3 -0
@@ -16,6 +16,7 @@ struct proc_ns_operations {struct ns_common *(*get)(struct task_struct *task);void (*put)(struct ns_common *ns);int (*install)(struct nsproxy *nsproxy,struct ns_common *ns); +void *(*get_type)(struct ns_common *ns); };extern const struct proc_ns_operations netns_operations;
@@ -66,6 +67,8 @@ static inline int ns_alloc_inum(struct ns_common *ns)#define ns_free_inum (ns) proc_free_inum((ns)->inum)extern struct file *proc_ns_fget (int fd); +extern void *proc_get_ns_by_fd (int fd,int type); +#define get_proc_ns (inode) ((struct ns_common *)(inode)->i_private)extern void *ns_get_path (struct path *path,struct task_struct *task,const struct proc_ns_operations *ns_ops);
kernel/pid_namespace.c +6 -0
@@ -388,12 +388,18 @@ static int pidns_install(struct nsproxy *nsproxy, struct ns_common *ns)return 0 ; } +static void *pidns_get_type (struct ns_common *ns) +{ +return get_pid_ns (to_pid_ns (ns)); +} +const struct proc_ns_operations pidns_operations = { .name ="pid" , .type =CLONE_NEWPID , .get = pidns_get, .put = pidns_put, .install = pidns_install, + .get_type = pidns_get_type, };static __init int pid_namespaces_init (void )
net/core/net_namespace.c +7 -16
@@ -420,22 +420,7 @@ EXPORT_SYMBOL_GPL(__put_net);struct net *get_net_ns_by_fd (int fd) { -struct file *file; -struct ns_common *ns; -struct net *net; - - file =proc_ns_fget (fd); -if (IS_ERR (file)) -return ERR_CAST (file); - - ns =get_proc_ns (file_inode (file)); -if (ns->ops == &netns_operations) - net = get_net(container_of(ns, struct net, ns)); -else - net =ERR_PTR (-EINVAL ); - -fput (file); -return net; +return proc_get_ns_by_fd (fd,CLONE_NEWNET ); }#else
@@ -955,11 +940,17 @@ static int netns_install(struct nsproxy *nsproxy, struct ns_common *ns) return 0; } +static void *netns_get_type (struct ns_common *ns) +{ +return get_net (to_net_ns (ns)); +} +const struct proc_ns_operations netns_operations = { .name ="net" , .type =CLONE_NEWNET , .get = netns_get, .put = netns_put, .install = netns_install, + .get_type = netns_get_type, };#endif
Signature · 1 line
1.5.5.1
kbuild test robot
build botRe: [PATCH RFC v3 2/2] pidns: introduce syscall getvpid
In reply to Konstantin Khlebnikovconfig: openrisc-or1ksim_defconfig (attached as .config) reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x…
Hi Konstantin,
[auto build test results on next-20150925 -- if it's inappropriate base, please ignore]
config: openrisc-or1ksim_defconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
git checkout 7bea85b3c058d69527d79b94338025f218a0655e
# save the attached .config to linux build tree make.cross ARCH=openrisc
All warnings (new ones prefixed by >>):
In file included from include/asm-generic/unistd.h:1:0,
from arch/openrisc/include/uapi/asm/unistd.h:26,
from <stdin>:2:
>> include/uapi/asm-generic/unistd.h:718:0: warning: "__NR_mlock2" redefined include/uapi/asm-generic/unistd.h:716:0: note: this is the location of the previous definition <stdin>:1307:2: warning: #warning syscall getvpid not implemented
--
In file included from include/asm-generic/unistd.h:1:0,
from arch/openrisc/include/uapi/asm/unistd.h:26,
from include/uapi/linux/unistd.h:7,
from arch/openrisc/kernel/setup.c:25:
>> include/uapi/asm-generic/unistd.h:718:0: warning: "__NR_mlock2" redefined
include/uapi/asm-generic/unistd.h:716:0: note: this is the location of the previous definition
--
In file included from include/asm-generic/unistd.h:1:0,
from arch/openrisc/include/uapi/asm/unistd.h:26,
from include/uapi/linux/unistd.h:7,
from include/linux/syscalls.h:78,
from arch/openrisc/kernel/sys_call_table.c:17:
>> include/uapi/asm-generic/unistd.h:718:0: warning: "__NR_mlock2" redefined
include/uapi/asm-generic/unistd.h:716:0: note: this is the location of the previous definition
In file included from include/asm-generic/unistd.h:1:0,
from arch/openrisc/include/uapi/asm/unistd.h:26,
from arch/openrisc/kernel/sys_call_table.c:27:
include/uapi/asm-generic/unistd.h:716:0: warning: "__NR_mlock2" redefined
include/uapi/asm-generic/unistd.h:718:0: note: this is the location of the previous definition
>> include/uapi/asm-generic/unistd.h:718:0: warning: "__NR_mlock2" redefined include/uapi/asm-generic/unistd.h:716:0: note: this is the location of the previous definition include/uapi/asm-generic/unistd.h:719:1: error: '__NR_getvpid' undeclared here (not in a function) include/uapi/asm-generic/unistd.h:719:1: error: array index in initializer not of integer type include/uapi/asm-generic/unistd.h:719:1: error: (near initialization for 'sys_call_table')
--
kernel/time/Kconfig:155:warning: range is invalid
In file included from include/asm-generic/unistd.h:1:0,
from arch/openrisc/include/uapi/asm/unistd.h:26,
from <stdin>:2:
>> include/uapi/asm-generic/unistd.h:718:0: warning: "__NR_mlock2" redefined include/uapi/asm-generic/unistd.h:716:0: note: this is the location of the previous definition <stdin>:1307:2: warning: #warning syscall getvpid not implemented
vim +/__NR_mlock2 +718 include/uapi/asm-generic/unistd.h
702 #define __NR_seccomp 277
703 __SYSCALL(__NR_seccomp, sys_seccomp)
704 #define __NR_getrandom 278
705 __SYSCALL(__NR_getrandom, sys_getrandom)
706 #define __NR_memfd_create 279
707 __SYSCALL(__NR_memfd_create, sys_memfd_create)
708 #define __NR_bpf 280
709 __SYSCALL(__NR_bpf, sys_bpf)
710 #define __NR_execveat 281
711 __SC_COMP(__NR_execveat, sys_execveat, compat_sys_execveat)
712 #define __NR_userfaultfd 282
713 __SYSCALL(__NR_userfaultfd, sys_userfaultfd)
714 #define __NR_membarrier 283
715 __SYSCALL(__NR_membarrier, sys_membarrier)
716 #define __NR_mlock2 284
717 __SYSCALL(__NR_mlock2, sys_mlock2)
> 718 #define __NR_mlock2 285
719 __SYSCALL(__NR_getvpid, sys_getvpid)
720
721 #undef __NR_syscalls
722 #define __NR_syscalls 286
723
724 /*
725 * All syscalls below here should go away really,
726 * these are provided for both review and as a porting
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
_______________________________________________
Containers mailing list Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/containers
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to Oleg NesterovQuoted 34 lines · Oleg Nesterov
Quoted 20 lines · Konstantin Khlebnikov
fs/nsfs.c +10
-4+struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref) { -struct file *file; +struct ns_common *ns; +struct fd f; - file =fget (fd); -if (!file) + f =fdget (fd); +if (!f.file)return ERR_PTR (-EBADF ); -if (file->f_op != &ns_file_operations) +if (f.file->f_op != &ns_file_operations) + goto out_invalid; + + ns =get_proc_ns (file_inode (f.file)); +if (nstype && (ns->ops->type != nstype)) goto out_invalid;fs/nsfs.c int ns_get_name(char *buf, size_t size, struct task_struct *task, · line 144
Quoted 10 lines
fs/nsfs.c +3
-2-return file; + *fd_ref = f; +return ns; out_invalid: -fput (file); +fdput (f);return ERR_PTR (-EINVAL ); }Well yes,
fdget()makes sense but this is minor.
Quoted 4 lines
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().
Hmm. My version has 0 or 2 atomic ops per get-put sequence. Your version: 2 or 4 atomic ops. Plus even in worst case pinning by struct fd theoretically scales better because it touches refcount at struct file: there're might be many of them for one namespace.
Quoted 7 lines
Eric, what do you think?
See also "TODO" in the changelog.
Oleg.
Signature · 1 line
Konstantin
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to a message not in the archiveQuoted 34 lines · Oleg Nesterov
Quoted 20 lines · Konstantin Khlebnikov
fs/nsfs.c +10
-4+struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref) { -struct file *file; +struct ns_common *ns; +struct fd f; - file =fget (fd); -if (!file) + f =fdget (fd); +if (!f.file)return ERR_PTR (-EBADF ); -if (file->f_op != &ns_file_operations) +if (f.file->f_op != &ns_file_operations) + goto out_invalid; + + ns =get_proc_ns (file_inode (f.file)); +if (nstype && (ns->ops->type != nstype)) goto out_invalid;fs/nsfs.c int ns_get_name(char *buf, size_t size, struct task_struct *task, · line 144
Quoted 10 lines
fs/nsfs.c +3
-2-return file; + *fd_ref = f; +return ns; out_invalid: -fput (file); +fdput (f);return ERR_PTR (-EINVAL ); }Well yes,
fdget()makes sense but this is minor.
Quoted 4 lines
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().
Hmm. My version has 0 or 2 atomic ops per get-put sequence. Your version: 2 or 4 atomic ops. Plus even in worst case pinning by struct fd theoretically scales better because it touches refcount at struct file: there're might be many of them for one namespace.
Quoted 7 lines
Eric, what do you think?
See also "TODO" in the changelog.
Oleg.
Signature · 1 line
Konstantin
Re: [PATCH RFC v3 2/2] pidns: introduce syscall getvpid
In reply to Konstantin KhlebnikovQuoted 5 lines · Konstantin Khlebnikov
pid_tgetvpid(pid_t pid, int source, int target);This syscall converts pid from source pid-namespace into pid visible in target pid-namespace. If pid is unreachable from target namespace then
getvpid()returns zero.
Two minor things.
Can we please call this translate_pid? getvpid does not really cover what this syscall does.
Can you please split wiring up into a separate patch? You goofed it up this round and it just adds noise in reviewing the core syscall.
Quoted 173 lines
Namespaces are defined by file descriptors pointing to entries in proc (/proc/[pid]/ns/pid). If argument is negative then current pid namespace is used.
If pid is negative then
getvpid()returns pid of parent task for -pid.Possible error codes:
ESRCH - task not found EBADF - closed file descriptor EINVAL - not pid-namespace file descriptorSuch conversion is required for interaction between processes from different pid-namespaces. For example system service at host system who provide access to restricted set of privileged operations for clients from containers have to convert pids back and forward.
Recent kernels expose virtual pids in /proc/[pid]/status:NSpid, but this interface works only in one way and even that is non-trivial.
Other option is passing pids with credentials via unix socket, but this solution requires a lot of preparation and
CAP_SYS_ADMINfor sending arbitrary pids.This syscall works in both directions, it's fast and simple.
Examples:
getvpid(pid, ns, -1) - get pid in our pid namespace getvpid(pid, -1, ns) - get pid in container getvpid(pid, -1, ns) > 0 - is pid is reachable from container? getvpid(1, ns1, ns2) > 0 - is ns1 inside ns2? getvpid(1, ns1, ns2) == 0 - is ns1 outside ns2? getvpid(1, ns, -1) - get init task of pid-namespace getvpid(-1, ns, -1) - get reaper of init task in parent pid-namespace getvpid(-pid, -1, -1) - get ppid by pidSigned-off-by Konstantin Khlebnikov <[email protected]>--
v1: https://lkml.org/lkml/2015/9/15/411
v2: https://lkml.org/lkml/2015/9/24/278
v3:
* useproc_ns_fdget()
* update description
* rebase to next-20150925
* fix conflict with mlock2--- arch/x86/entry/syscalls/syscall_32.tbl | 1 + arch/x86/entry/syscalls/syscall_64.tbl | 1 + include/linux/syscalls.h | 1 + include/uapi/asm-generic/unistd.h | 4 ++- kernel/sys.c | 51 ++++++++++++++++++++++++++++++++ 5 files changed, 57 insertions(+), 1 deletion(-)arch/x86/entry/syscalls/syscall_32.tbl +1
-0@@ -383,3 +383,4 @@ 374 i386 userfaultfd sys_userfaultfd 375 i386 membarrier sys_membarrier 376 i386 mlock2 sys_mlock2 +377 i386 getvpid sys_getvpidarch/x86/entry/syscalls/syscall_64.tbl +1
-0@@ -332,6 +332,7 @@ 323 common userfaultfd sys_userfaultfd 324 common membarrier sys_membarrier 325 common mlock2 sys_mlock2 +326 common getvpid sys_getvpid # # x32-specific system call numbers start at 512 to avoid cache impactinclude/linux/syscalls.h +1
-0@@ -222,6 +222,7 @@ asmlinkage long sys_nanosleep(struct timespec __user *rqtp, struct timespec __usasmlinkage long sys_alarm (unsigned int seconds);asmlinkage long sys_getpid (void );asmlinkage long sys_getppid (void ); +asmlinkage long sys_getvpid (pid_t pid,int source,int target);asmlinkage long sys_getuid (void );asmlinkage long sys_geteuid (void );asmlinkage long sys_getgid (void );include/uapi/asm-generic/unistd.h +3
-1@@ -715,9 +715,11 @@ __SYSCALL(__NR_userfaultfd, sys_userfaultfd) __SYSCALL(__NR_membarrier, sys_membarrier)#define __NR_mlock2 284 __SYSCALL(__NR_mlock2, sys_mlock2) +#define __NR_mlock2 285 +__SYSCALL(__NR_getvpid, sys_getvpid)#undef __NR_syscalls -#define __NR_syscalls 285 +#define __NR_syscalls 286/* * All syscalls below here should go away really, kernel/sys.c +51
-0@@ -46,6 +46,7 @@#include <linux/syscalls.h> #include <linux/kprobes.h> #include <linux/user_namespace.h> +#include <linux/proc_ns.h> #include <linux/binfmts.h> #include <linux/sched.h> @@ -855,6 +856,56 @@ SYSCALL_DEFINE0(getppid)return pid; } +SYSCALL_DEFINE3(getvpid, pid_t, pid, int, source, int, target) +{ +struct pid_namespace *source_ns, *target_ns; +struct fd source_fd = {}, target_fd = {}; +struct pid *struct_pid; +struct ns_common *ns; +pid_t result; + +if (source >=0 ) { + ns =proc_ns_fdget (source,CLONE_NEWPID , &source_fd); + result =PTR_ERR (ns); +if (IS_ERR (ns)) + goto out; + source_ns = container_of(ns, struct pid_namespace, ns); + }else + source_ns =task_active_pid_ns (current); + +if (target >=0 ) { + ns =proc_ns_fdget (target,CLONE_NEWPID , &target_fd); + result =PTR_ERR (ns); +if (IS_ERR (ns)) + goto out; + target_ns = container_of(ns, struct pid_namespace, ns); + }else + target_ns =task_active_pid_ns (current); + +rcu_read_lock (); + struct_pid =find_pid_ns (abs (pid), source_ns); + +if (struct_pid && pid <0 ) { +struct task_struct *task; + + task =pid_task (struct_pid,PIDTYPE_PID ); +if (task) + task =rcu_dereference (task->real_parent); + struct_pid = task ?task_pid (task) :NULL ; + } + +if (struct_pid) + result =pid_nr_ns (struct_pid, target_ns); +else + result = -ESRCH ; +rcu_read_unlock (); + +out: +fdput (target_fd); +fdput (source_fd); +return result; +} +SYSCALL_DEFINE0 (getuid) {/* Only we change this so SMP safe */
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to a message not in the archiveQuoted 34 lines · Oleg Nesterov
Quoted 20 lines · Konstantin Khlebnikov
fs/nsfs.c +10
-4+struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref) { -struct file *file; +struct ns_common *ns; +struct fd f; - file =fget (fd); -if (!file) + f =fdget (fd); +if (!f.file)return ERR_PTR (-EBADF ); -if (file->f_op != &ns_file_operations) +if (f.file->f_op != &ns_file_operations) + goto out_invalid; + + ns =get_proc_ns (file_inode (f.file)); +if (nstype && (ns->ops->type != nstype)) goto out_invalid;fs/nsfs.c int ns_get_name(char *buf, size_t size, struct task_struct *task, · line 144
Quoted 10 lines
fs/nsfs.c +3
-2-return file; + *fd_ref = f; +return ns; out_invalid: -fput (file); +fdput (f);return ERR_PTR (-EINVAL ); }Well yes,
fdget()makes sense but this is minor.
Quoted 6 lines
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().Eric, what do you think?
At some level I don't care this is not exposed to userspace.
However since we are going several rounds with this.
Of the existing uses several of them sleep, which unfortunately means we can not use rcu locking for everything. The network namespace ones wind up taking a reference to struct net because the have the legacy pid case to deal with. Which makes we can not use fdget for all callers either.
For this translate_pid rcu locking is sufficient, rcu locking is easy and doing any more than rcu locking just seems silly. So let me respectfully suggest.
struct ns_common *ns_by_fd_rcu(int fd, int type)
{
struct files_struct *files = current->files;
struct file *file;
struct ns_common *ns;
void *ret;
file = fcheck_files(files, fd);
if (!file)
return ERR_PTR(-EBADF);
if (file->f_mode & FMODE_PATH)
return ERR_PTR(-EINVAL);
if (file->f_op != &ns_file_operations)
return ERR_PTR(-EINVAL);
ns = get_proc_ns(file_inode(file));
if (ns->ops->type != type)
return ERR_PTR(-EINVAL);
return ns;
}struct pid_namespace *pidns_by_fd_rcu(int fd)
{
struct ns_common *ns = ns_by_fd_rcu(fd, CLONE_NEWPID);
if (IS_ERR(ns))
return ERR_CAST(ns);
return container_of(ns, struct pid_namespace, ns);
}SYSCALL_DEFINE3(translate_pid, pid_t, pid_nr, int, sourcefd, int, targetfd)
{
struct pid_namespace *source, *target;
struct pid *pid;
pid_t result;
rcu_read_lock();
if (sourcefd >= 0)
source = pidns_by_fd_rcu(sourcefd);
else
source = task_active_pid_ns(current);
if (targetfd >= 0)
target = pidns_by_fd_rcu(targetfd);
else
target = task_active_pid_ns(current);
pid = find_pid_ns(pid_nr, source);
result = pid_nr_ns(pid, target);
if (result == 0)
result = -ESRCH;
rcu_read_unlock();
return result;
}Eric
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to Oleg NesterovQuoted 34 lines · Oleg Nesterov
Quoted 20 lines · Konstantin Khlebnikov
fs/nsfs.c +10
-4+struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref) { -struct file *file; +struct ns_common *ns; +struct fd f; - file =fget (fd); -if (!file) + f =fdget (fd); +if (!f.file)return ERR_PTR (-EBADF ); -if (file->f_op != &ns_file_operations) +if (f.file->f_op != &ns_file_operations) + goto out_invalid; + + ns =get_proc_ns (file_inode (f.file)); +if (nstype && (ns->ops->type != nstype)) goto out_invalid;fs/nsfs.c int ns_get_name(char *buf, size_t size, struct task_struct *task, · line 144
Quoted 10 lines
fs/nsfs.c +3
-2-return file; + *fd_ref = f; +return ns; out_invalid: -fput (file); +fdput (f);return ERR_PTR (-EINVAL ); }Well yes,
fdget()makes sense but this is minor.
Quoted 6 lines
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().Eric, what do you think?
At some level I don't care this is not exposed to userspace.
However since we are going several rounds with this.
Of the existing uses several of them sleep, which unfortunately means we can not use rcu locking for everything. The network namespace ones wind up taking a reference to struct net because the have the legacy pid case to deal with. Which makes we can not use fdget for all callers either.
For this translate_pid rcu locking is sufficient, rcu locking is easy and doing any more than rcu locking just seems silly. So let me respectfully suggest.
struct ns_common *ns_by_fd_rcu(int fd, int type)
{
struct files_struct *files = current->files;
struct file *file;
struct ns_common *ns;
void *ret;
file = fcheck_files(files, fd);
if (!file)
return ERR_PTR(-EBADF);
if (file->f_mode & FMODE_PATH)
return ERR_PTR(-EINVAL);
if (file->f_op != &ns_file_operations)
return ERR_PTR(-EINVAL);
ns = get_proc_ns(file_inode(file));
if (ns->ops->type != type)
return ERR_PTR(-EINVAL);
return ns;
}struct pid_namespace *pidns_by_fd_rcu(int fd)
{
struct ns_common *ns = ns_by_fd_rcu(fd, CLONE_NEWPID);
if (IS_ERR(ns))
return ERR_CAST(ns);
return container_of(ns, struct pid_namespace, ns);
}SYSCALL_DEFINE3(translate_pid, pid_t, pid_nr, int, sourcefd, int, targetfd)
{
struct pid_namespace *source, *target;
struct pid *pid;
pid_t result;
rcu_read_lock();
if (sourcefd >= 0)
source = pidns_by_fd_rcu(sourcefd);
else
source = task_active_pid_ns(current);
if (targetfd >= 0)
target = pidns_by_fd_rcu(targetfd);
else
target = task_active_pid_ns(current);
pid = find_pid_ns(pid_nr, source);
result = pid_nr_ns(pid, target);
if (result == 0)
result = -ESRCH;
rcu_read_unlock();
return result;
}Eric
Re: [PATCH RFC v3 2/2] pidns: introduce syscall getvpid
In reply to Konstantin KhlebnikovQuoted 1 line · Konstantin Khlebnikov
If pid is negative then
getvpid()returns pid of parent task for -pid.
Now that I am noticing this. I don't think I have seen any discussion about justifying a syscall getting another processes parent pid. My apologies if I just missed it.
Why do we want the the parent pid? We can we usefully do with it? Is proc really that bad of an interface?
Fetching a parent pid feels like a separate logical operation from pid translation. Which makes me a bit uneasy about this part of the conversation.
Quoted 9 lines
Examples:
getvpid(pid, ns, -1) - get pid in our pid namespace getvpid(pid, -1, ns) - get pid in container getvpid(pid, -1, ns) > 0 - is pid is reachable from container? getvpid(1, ns1, ns2) > 0 - is ns1 inside ns2? getvpid(1, ns1, ns2) == 0 - is ns1 outside ns2? getvpid(1, ns, -1) - get init task of pid-namespace getvpid(-1, ns, -1) - get reaper of init task in parent pid-namespace getvpid(-pid, -1, -1) - get ppid by pid
As I step back and pay attention to this case I am half wondering if perhaps what would be most useful is a file descriptor that refers to a pid and an updated set of system calls that takes pid file descriptors instead of pids.
Something like:
getpidfd(int pidnsfd, pid_t pid);
waitfd(int pidfd, int *status, int options, struct rusage *rusage);
killfd(int pidfd, int sig);
clonefd(...);And perhaps:
pid_nr_ns(int pidnsfd, int pidfd);
parentfd(int pidfd);Eric
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to Eric W. BiedermanQuoted 11 lines · Eric W. Biederman
Quoted 6 lines · Oleg Nesterov
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().Eric, what do you think?
At some level I don't care this is not exposed to userspace.
I agree, this is minor. But you know, the kernel is already complicated too much, we should try to simplify/cleanup everything we can ;)
Quoted 4 lines
Of the existing uses several of them sleep, which unfortunately means we can not use rcu locking for everything. The network namespace ones wind up taking a reference to struct net because the have the legacy pid case to deal with. Which makes we can not use fdget for all callers either.
And that is why 1/1 adds proc_get_ns_by_fd/get_type which can also be used by the network namespace.
Quoted 19 lines
For this
translate_pidrcu locking is sufficient, rcu locking is easy and doing any more than rcu locking just seems silly. So let me respectfully suggest.struct
ns_common*ns_by_fd_rcu(int fd, int type){ struct files_struct *files = current->files; struct file *file; struct ns_common *ns; void *ret; file = fcheck_files(files, fd); if (!file) return ERR_PTR(-EBADF); if (file->f_mode & FMODE_PATH) return ERR_PTR(-EINVAL); if (file->f_op != &ns_file_operations)
Quoted 8 lines
return ERR_PTR(-EINVAL); ns = get_proc_ns(file_inode(file)); if (ns->ops->type != type) return ERR_PTR(-EINVAL); return ns; }
OK, I won't insist, this too looks better to me than proc_ns_fdget(&fd_ref).
And in any case fcheck_files() makes more sense than fdget(), somehow I did not think about this when I sent 1/1.
Hmm. and after the quick look at cleanup_net() I can't understand whether get_net_ns_by_fd() can use ns_by_fd_rcu() + maybe_get_net(to_net_ns()) or not... Can it?
Oleg.
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to a message not in the archiveQuoted 11 lines · Eric W. Biederman
Quoted 6 lines · Oleg Nesterov
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().Eric, what do you think?
At some level I don't care this is not exposed to userspace.
I agree, this is minor. But you know, the kernel is already complicated too much, we should try to simplify/cleanup everything we can ;)
Quoted 4 lines
Of the existing uses several of them sleep, which unfortunately means we can not use rcu locking for everything. The network namespace ones wind up taking a reference to struct net because the have the legacy pid case to deal with. Which makes we can not use fdget for all callers either.
And that is why 1/1 adds proc_get_ns_by_fd/get_type which can also be used by the network namespace.
Quoted 19 lines
For this
translate_pidrcu locking is sufficient, rcu locking is easy and doing any more than rcu locking just seems silly. So let me respectfully suggest.struct
ns_common*ns_by_fd_rcu(int fd, int type){ struct files_struct *files = current->files; struct file *file; struct ns_common *ns; void *ret; file = fcheck_files(files, fd); if (!file) return ERR_PTR(-EBADF); if (file->f_mode & FMODE_PATH) return ERR_PTR(-EINVAL); if (file->f_op != &ns_file_operations)
Quoted 8 lines
return ERR_PTR(-EINVAL); ns = get_proc_ns(file_inode(file)); if (ns->ops->type != type) return ERR_PTR(-EINVAL); return ns; }
OK, I won't insist, this too looks better to me than proc_ns_fdget(&fd_ref).
And in any case fcheck_files() makes more sense than fdget(), somehow I did not think about this when I sent 1/1.
Hmm. and after the quick look at cleanup_net() I can't understand whether get_net_ns_by_fd() can use ns_by_fd_rcu() + maybe_get_net(to_net_ns()) or not... Can it?
Oleg.
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to Oleg NesterovQuoted 52 lines · Oleg Nesterov
Quoted 11 lines · Eric W. Biederman
Quoted 6 lines · Oleg Nesterov
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().Eric, what do you think?
At some level I don't care this is not exposed to userspace.
I agree, this is minor. But you know, the kernel is already complicated too much, we should try to simplify/cleanup everything we can ;)
Quoted 4 lines
Of the existing uses several of them sleep, which unfortunately means we can not use rcu locking for everything. The network namespace ones wind up taking a reference to struct net because the have the legacy pid case to deal with. Which makes we can not use fdget for all callers either.
And that is why 1/1 adds proc_get_ns_by_fd/get_type which can also be used by the network namespace.
Quoted 19 lines
For this
translate_pidrcu locking is sufficient, rcu locking is easy and doing any more than rcu locking just seems silly. So let me respectfully suggest.struct
ns_common*ns_by_fd_rcu(int fd, int type){ struct files_struct *files = current->files; struct file *file; struct ns_common *ns; void *ret; file = fcheck_files(files, fd); if (!file) return ERR_PTR(-EBADF); if (file->f_mode & FMODE_PATH) return ERR_PTR(-EINVAL); if (file->f_op != &ns_file_operations)Quoted 8 lines
return ERR_PTR(-EINVAL); ns = get_proc_ns(file_inode(file)); if (ns->ops->type != type) return ERR_PTR(-EINVAL); return ns; }
Quoted 8 lines
OK, I won't insist, this too looks better to me than
proc_ns_fdget(&fd_ref).And in any case
fcheck_files()makes more sense thanfdget(), somehow I did not think about this when I sent 1/1.Hmm. and after the quick look at
cleanup_net()I can't understand whetherget_net_ns_by_fd()can usens_by_fd_rcu()+ maybe_get_net(to_net_ns()) or not... Can it?
Some of those places need a reference that allows them to sleep, and the code is shared with the legacy pid case so with an addition of get_net
we can use ns_by_fd_rcu(). There are cases like setns that could
use ns_by_fd_rcu() with code reording.
We can implement get_net_ns_by_fd as:
struct net *get_net_ns_by_fd(int fd)
{
struct net *net;
rcu_read_lock();
net = net_ns_by_fd_rcu(fd);
if (!IS_ERR(net))
get_net(net);
rcu_read_unlock();
return net;
}Which means we can achieve code sharing with the pure rcu version as a base.
If the networking code did not have the legacy pid case to handle I would want to do something with struct fd, as the file descriptor already keeps the struct net reference alive and struct fd allows for sleeping.
Eric
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to a message not in the archiveQuoted 52 lines · Oleg Nesterov
Quoted 11 lines · Eric W. Biederman
Quoted 6 lines · Oleg Nesterov
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().Eric, what do you think?
At some level I don't care this is not exposed to userspace.
I agree, this is minor. But you know, the kernel is already complicated too much, we should try to simplify/cleanup everything we can ;)
Quoted 4 lines
Of the existing uses several of them sleep, which unfortunately means we can not use rcu locking for everything. The network namespace ones wind up taking a reference to struct net because the have the legacy pid case to deal with. Which makes we can not use fdget for all callers either.
And that is why 1/1 adds proc_get_ns_by_fd/get_type which can also be used by the network namespace.
Quoted 19 lines
For this
translate_pidrcu locking is sufficient, rcu locking is easy and doing any more than rcu locking just seems silly. So let me respectfully suggest.struct
ns_common*ns_by_fd_rcu(int fd, int type){ struct files_struct *files = current->files; struct file *file; struct ns_common *ns; void *ret; file = fcheck_files(files, fd); if (!file) return ERR_PTR(-EBADF); if (file->f_mode & FMODE_PATH) return ERR_PTR(-EINVAL); if (file->f_op != &ns_file_operations)Quoted 8 lines
return ERR_PTR(-EINVAL); ns = get_proc_ns(file_inode(file)); if (ns->ops->type != type) return ERR_PTR(-EINVAL); return ns; }
Quoted 8 lines
OK, I won't insist, this too looks better to me than
proc_ns_fdget(&fd_ref).And in any case
fcheck_files()makes more sense thanfdget(), somehow I did not think about this when I sent 1/1.Hmm. and after the quick look at
cleanup_net()I can't understand whetherget_net_ns_by_fd()can usens_by_fd_rcu()+ maybe_get_net(to_net_ns()) or not... Can it?
Some of those places need a reference that allows them to sleep, and the code is shared with the legacy pid case so with an addition of get_net
we can use ns_by_fd_rcu(). There are cases like setns that could
use ns_by_fd_rcu() with code reording.
We can implement get_net_ns_by_fd as:
struct net *get_net_ns_by_fd(int fd)
{
struct net *net;
rcu_read_lock();
net = net_ns_by_fd_rcu(fd);
if (!IS_ERR(net))
get_net(net);
rcu_read_unlock();
return net;
}Which means we can achieve code sharing with the pure rcu version as a base.
If the networking code did not have the legacy pid case to handle I would want to do something with struct fd, as the file descriptor already keeps the struct net reference alive and struct fd allows for sleeping.
Eric
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to Eric W. BiedermanQuoted 31 lines · Eric W. Biederman
Quoted 8 lines · Oleg Nesterov
OK, I won't insist, this too looks better to me than
proc_ns_fdget(&fd_ref).And in any case
fcheck_files()makes more sense thanfdget(), somehow I did not think about this when I sent 1/1.Hmm. and after the quick look at
cleanup_net()I can't understand whetherget_net_ns_by_fd()can usens_by_fd_rcu()+ maybe_get_net(to_net_ns()) or not... Can it?Some of those places need a reference that allows them to sleep, and the code is shared with the legacy pid case so with an addition of
get_net
we can usens_by_fd_rcu(). There are cases like setns that could
usens_by_fd_rcu()with code reording.We can implement
get_net_ns_by_fdas:
struct net *get_net_ns_by_fd(int fd){ struct net *net; rcu_read_lock(); net = net_ns_by_fd_rcu(fd); if (!IS_ERR(net)) get_net(net); rcu_read_unlock(); return net; }
Quoted 2 lines
Which means we can achieve code sharing with the pure rcu version as a base.
Yes, this is what I meant... but don't we need maybe_get_net() ?
Oleg.
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to a message not in the archiveQuoted 31 lines · Eric W. Biederman
Quoted 8 lines · Oleg Nesterov
OK, I won't insist, this too looks better to me than
proc_ns_fdget(&fd_ref).And in any case
fcheck_files()makes more sense thanfdget(), somehow I did not think about this when I sent 1/1.Hmm. and after the quick look at
cleanup_net()I can't understand whetherget_net_ns_by_fd()can usens_by_fd_rcu()+ maybe_get_net(to_net_ns()) or not... Can it?Some of those places need a reference that allows them to sleep, and the code is shared with the legacy pid case so with an addition of
get_net
we can usens_by_fd_rcu(). There are cases like setns that could
usens_by_fd_rcu()with code reording.We can implement
get_net_ns_by_fdas:
struct net *get_net_ns_by_fd(int fd){ struct net *net; rcu_read_lock(); net = net_ns_by_fd_rcu(fd); if (!IS_ERR(net)) get_net(net); rcu_read_unlock(); return net; }
Quoted 2 lines
Which means we can achieve code sharing with the pure rcu version as a base.
Yes, this is what I meant... but don't we need maybe_get_net() ?
Oleg.
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to Oleg NesterovQuoted 29 lines · Oleg Nesterov
Quoted 28 lines · Eric W. Biederman
Quoted 8 lines · Oleg Nesterov
OK, I won't insist, this too looks better to me than
proc_ns_fdget(&fd_ref).And in any case
fcheck_files()makes more sense thanfdget(), somehow I did not think about this when I sent 1/1.Hmm. and after the quick look at
cleanup_net()I can't understand whetherget_net_ns_by_fd()can usens_by_fd_rcu()+ maybe_get_net(to_net_ns()) or not... Can it?Some of those places need a reference that allows them to sleep, and the code is shared with the legacy pid case so with an addition of
get_net
we can usens_by_fd_rcu(). There are cases like setns that could
usens_by_fd_rcu()with code reording.We can implement
get_net_ns_by_fdas:
struct net *get_net_ns_by_fd(int fd){ struct net *net; rcu_read_lock(); net = net_ns_by_fd_rcu(fd); if (!IS_ERR(net)) get_net(net); rcu_read_unlock();
Quoted 7 lines
Quoted 5 lines
return net; }Which means we can achieve code sharing with the pure rcu version as a base.
Yes, this is what I meant... but don't we need
maybe_get_net()?
Let me see.
The call chain is a little interesting so let's trace it.
thread1 thread2
net = net_ns_by_fd_rcu(fd); fput(file)
get_net(net); ____fput
__fput
dput
dentry_kill
__dentry_kill
dentry_iput
iput
iput_final
evict
->evict_inode (nsfs_evict)
netns_put
put_net
__put_net
queue_work(net_cleanup_work)
...
cleanup_net
synchronize_rcu.Given that someone in another thread can put the file descriptor and I don't see anything explicitly waiting until after the rcu critical section ends to put the network namespace I guess we do need maybe_get_net.
In practice I think the delay logic in fput will act as an rcu barrier, but that is not guaranteed so we had better not count on it. Sigh.
Anyway this is a long ways from a syscall to translate pids.
Eric
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to a message not in the archiveQuoted 53 lines · Eric W. Biederman
Quoted 32 lines · Oleg Nesterov
Quoted 19 lines · Konstantin Khlebnikov
fs/nsfs.c +10
-4+struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref) { -struct file *file; +struct ns_common *ns; +struct fd f; - file =fget (fd); -if (!file) + f =fdget (fd); +if (!f.file)return ERR_PTR (-EBADF ); -if (file->f_op != &ns_file_operations) +if (f.file->f_op != &ns_file_operations) + goto out_invalid; + + ns =get_proc_ns (file_inode (f.file)); +if (nstype && (ns->ops->type != nstype)) goto out_invalid;fs/nsfs.c int ns_get_name(char *buf, size_t size, struct task_struct *task, · line 144
Quoted 10 lines
fs/nsfs.c +3
-2-return file; + *fd_ref = f; +return ns; out_invalid: -fput (file); +fdput (f);return ERR_PTR (-EINVAL ); }Well yes,
fdget()makes sense but this is minor.Quoted 6 lines
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().Eric, what do you think?
At some level I don't care this is not exposed to userspace.
However since we are going several rounds with this.
Of the existing uses several of them sleep, which unfortunately means we can not use rcu locking for everything. The network namespace ones wind up taking a reference to struct net because the have the legacy pid case to deal with. Which makes we can not use fdget for all callers either.
For this
translate_pidrcu locking is sufficient, rcu locking is easy and doing any more than rcu locking just seems silly. So let me respectfully suggest.
Quoted 6 lines
struct
ns_common*ns_by_fd_rcu(int fd, int type){ struct files_struct *files = current->files; struct file *file; struct ns_common *ns; void *ret;
pointer files seems no more useful. we can
use fcheck(fd) instead.
Thanks,
Quoted 57 lines
file = fcheck_files(files, fd); if (!file) return ERR_PTR(-EBADF); if (file->f_mode & FMODE_PATH) return ERR_PTR(-EINVAL); if (file->f_op != &ns_file_operations) return ERR_PTR(-EINVAL); ns = get_proc_ns(file_inode(file)); if (ns->ops->type != type) return ERR_PTR(-EINVAL); return ns; }struct
pid_namespace*pidns_by_fd_rcu(int fd){ struct ns_common *ns = ns_by_fd_rcu(fd, CLONE_NEWPID); if (IS_ERR(ns)) return ERR_CAST(ns); return container_of(ns, struct pid_namespace, ns); }
SYSCALL_DEFINE3(translate_pid, pid_t, pid_nr, int, sourcefd, int, targetfd){ struct pid_namespace *source, *target; struct pid *pid; pid_t result; rcu_read_lock(); if (sourcefd >= 0) source = pidns_by_fd_rcu(sourcefd); else source = task_active_pid_ns(current); if (targetfd >= 0) target = pidns_by_fd_rcu(targetfd); else target = task_active_pid_ns(current); pid = find_pid_ns(pid_nr, source); result = pid_nr_ns(pid, target); if (result == 0) result = -ESRCH; rcu_read_unlock(); return result; }Eric
.
Re: [PATCH 0/1] ns: introduce proc_get_ns_by_fd()
In reply to Eric W. BiedermanQuoted 53 lines · Eric W. Biederman
Quoted 32 lines · Oleg Nesterov
Quoted 19 lines · Konstantin Khlebnikov
fs/nsfs.c +10
-4+struct ns_common *proc_ns_fdget (int fd,int nstype,struct fd *fd_ref) { -struct file *file; +struct ns_common *ns; +struct fd f; - file =fget (fd); -if (!file) + f =fdget (fd); +if (!f.file)return ERR_PTR (-EBADF ); -if (file->f_op != &ns_file_operations) +if (f.file->f_op != &ns_file_operations) + goto out_invalid; + + ns =get_proc_ns (file_inode (f.file)); +if (nstype && (ns->ops->type != nstype)) goto out_invalid;fs/nsfs.c int ns_get_name(char *buf, size_t size, struct task_struct *task, · line 144
Quoted 10 lines
fs/nsfs.c +3
-2-return file; + *fd_ref = f; +return ns; out_invalid: -fput (file); +fdput (f);return ERR_PTR (-EINVAL ); }Well yes,
fdget()makes sense but this is minor.Quoted 6 lines
Honestly, I do not really like the new helper... I understand this is subjective, so I won't insist. But how about 1/1? We do not need fd/file at all. With this patch your
sys_getvpid()can just useproc_get_ns_by_fd(fd, CLONE_NEWPID)andput_pid_ns().Eric, what do you think?
At some level I don't care this is not exposed to userspace.
However since we are going several rounds with this.
Of the existing uses several of them sleep, which unfortunately means we can not use rcu locking for everything. The network namespace ones wind up taking a reference to struct net because the have the legacy pid case to deal with. Which makes we can not use fdget for all callers either.
For this
translate_pidrcu locking is sufficient, rcu locking is easy and doing any more than rcu locking just seems silly. So let me respectfully suggest.
Quoted 6 lines
struct
ns_common*ns_by_fd_rcu(int fd, int type){ struct files_struct *files = current->files; struct file *file; struct ns_common *ns; void *ret;
pointer files seems no more useful. we can
use fcheck(fd) instead.
Thanks,
Quoted 57 lines
file = fcheck_files(files, fd); if (!file) return ERR_PTR(-EBADF); if (file->f_mode & FMODE_PATH) return ERR_PTR(-EINVAL); if (file->f_op != &ns_file_operations) return ERR_PTR(-EINVAL); ns = get_proc_ns(file_inode(file)); if (ns->ops->type != type) return ERR_PTR(-EINVAL); return ns; }struct
pid_namespace*pidns_by_fd_rcu(int fd){ struct ns_common *ns = ns_by_fd_rcu(fd, CLONE_NEWPID); if (IS_ERR(ns)) return ERR_CAST(ns); return container_of(ns, struct pid_namespace, ns); }
SYSCALL_DEFINE3(translate_pid, pid_t, pid_nr, int, sourcefd, int, targetfd){ struct pid_namespace *source, *target; struct pid *pid; pid_t result; rcu_read_lock(); if (sourcefd >= 0) source = pidns_by_fd_rcu(sourcefd); else source = task_active_pid_ns(current); if (targetfd >= 0) target = pidns_by_fd_rcu(targetfd); else target = task_active_pid_ns(current); pid = find_pid_ns(pid_nr, source); result = pid_nr_ns(pid, target); if (result == 0) result = -ESRCH; rcu_read_unlock(); return result; }Eric
.
Re: [PATCH RFC v3 2/2] pidns: introduce syscall getvpid
In reply to Eric W. BiedermanQuoted 8 lines · Eric W. Biederman
Quoted 1 line · Konstantin Khlebnikov
If pid is negative then
getvpid()returns pid of parent task for -pid.Now that I am noticing this. I don't think I have seen any discussion about justifying a syscall getting another processes parent pid. My apologies if I just missed it.
Sorry for late response. This completely fell out of my mind after LinuxCon.
Quoted 6 lines
Why do we want the the parent pid? We can we usefully do with it? Is proc really that bad of an interface?
Fetching a parent pid feels like a separate logical operation from pid translation. Which makes me a bit uneasy about this part of the conversation.
Yep proc interface is bad. /proc/$pid/stat is almost impossible to parse without flaws because task could set second field "comm" into any string and fake ppid - for example ") Z 1". /proc/$pid/status is better but it has more information and thus slower.
This trick for distant getppid looks cheap useful:
in this interface space of negative pids is free for use.
Quoted 11 lines
Quoted 10 lines
Examples:
getvpid(pid, ns, -1) - get pid in our pid namespace getvpid(pid, -1, ns) - get pid in container getvpid(pid, -1, ns) > 0 - is pid is reachable from container? getvpid(1, ns1, ns2) > 0 - is ns1 inside ns2? getvpid(1, ns1, ns2) == 0 - is ns1 outside ns2? getvpid(1, ns, -1) - get init task of pid-namespace getvpid(-1, ns, -1) - get reaper of init task in parent pid-namespace getvpid(-pid, -1, -1) - get ppid by pid
Quoted 4 lines
As I step back and pay attention to this case I am half wondering if perhaps what would be most useful is a file descriptor that refers to a pid and an updated set of system calls that takes pid file descriptors instead of pids.
Fd which pins pids isn't a good idea.
I think it's better to refer (but not hold) task rather than pid. For example inode of taskfd will hold small buffer for task exit
status: task holds reference to its own taskfd inode and populates status when exits. Here will be no zombies and delayed reaping.
Something like:
task_fd = clonefd()
...
select(...)
exit(...)pread(task_fd, &status_rusage_etc, sizeof, 0);close(task_fd);
Task pid also could be part of structure in that fd. Potentially it could provide the same information as /proc/$pid/... in effective binary format: we can read only required fields of structure and kernel can skip unneeded calculations.
Quoted 18 lines
Something like:
getpidfd(int pidnsfd, pid_t pid); waitfd(int pidfd, int *status, int options, struct rusage *rusage); killfd(int pidfd, int sig); clonefd(...);And perhaps:
pid_nr_ns(int pidnsfd, int pidfd); parentfd(int pidfd);Eric
Signature · 1 line
Konstantin
Re: [PATCH RFC v3 2/2] pidns: introduce syscall getvpid
In reply to a message not in the archiveQuoted 8 lines · Eric W. Biederman
Quoted 1 line · Konstantin Khlebnikov
If pid is negative then
getvpid()returns pid of parent task for -pid.Now that I am noticing this. I don't think I have seen any discussion about justifying a syscall getting another processes parent pid. My apologies if I just missed it.
Sorry for late response. This completely fell out of my mind after LinuxCon.
Quoted 6 lines
Why do we want the the parent pid? We can we usefully do with it? Is proc really that bad of an interface?
Fetching a parent pid feels like a separate logical operation from pid translation. Which makes me a bit uneasy about this part of the conversation.
Yep proc interface is bad. /proc/$pid/stat is almost impossible to parse without flaws because task could set second field "comm" into any string and fake ppid - for example ") Z 1". /proc/$pid/status is better but it has more information and thus slower.
This trick for distant getppid looks cheap useful:
in this interface space of negative pids is free for use.
Quoted 11 lines
Quoted 10 lines
Examples:
getvpid(pid, ns, -1) - get pid in our pid namespace getvpid(pid, -1, ns) - get pid in container getvpid(pid, -1, ns) > 0 - is pid is reachable from container? getvpid(1, ns1, ns2) > 0 - is ns1 inside ns2? getvpid(1, ns1, ns2) == 0 - is ns1 outside ns2? getvpid(1, ns, -1) - get init task of pid-namespace getvpid(-1, ns, -1) - get reaper of init task in parent pid-namespace getvpid(-pid, -1, -1) - get ppid by pid
Quoted 4 lines
As I step back and pay attention to this case I am half wondering if perhaps what would be most useful is a file descriptor that refers to a pid and an updated set of system calls that takes pid file descriptors instead of pids.
Fd which pins pids isn't a good idea.
I think it's better to refer (but not hold) task rather than pid. For example inode of taskfd will hold small buffer for task exit
status: task holds reference to its own taskfd inode and populates status when exits. Here will be no zombies and delayed reaping.
Something like:
task_fd = clonefd()
...
select(...)
exit(...)pread(task_fd, &status_rusage_etc, sizeof, 0);close(task_fd);
Task pid also could be part of structure in that fd. Potentially it could provide the same information as /proc/$pid/... in effective binary format: we can read only required fields of structure and kernel can skip unneeded calculations.
Quoted 18 lines
Something like:
getpidfd(int pidnsfd, pid_t pid); waitfd(int pidfd, int *status, int options, struct rusage *rusage); killfd(int pidfd, int sig); clonefd(...);And perhaps:
pid_nr_ns(int pidnsfd, int pidfd); parentfd(int pidfd);Eric
Signature · 1 line
Konstantin