2008-02-08 15:18:22 +03:00
/*
* linux / ipc / namespace . c
* Copyright ( C ) 2006 Pavel Emelyanov < xemul @ openvz . org > OpenVZ , SWsoft Inc .
*/
# include <linux/ipc.h>
# include <linux/msg.h>
# include <linux/ipc_namespace.h>
# include <linux/rcupdate.h>
# include <linux/nsproxy.h>
# include <linux/slab.h>
namespaces: ipc namespaces: implement support for posix msqueues
Implement multiple mounts of the mqueue file system, and link it to usage
of CLONE_NEWIPC.
Each ipc ns has a corresponding mqueuefs superblock. When a user does
clone(CLONE_NEWIPC) or unshare(CLONE_NEWIPC), the unshare will cause an
internal mount of a new mqueuefs sb linked to the new ipc ns.
When a user does 'mount -t mqueue mqueue /dev/mqueue', he mounts the
mqueuefs superblock.
Posix message queues can be worked with both through the mq_* system calls
(see mq_overview(7)), and through the VFS through the mqueue mount. Any
usage of mq_open() and friends will work with the acting task's ipc
namespace. Any actions through the VFS will work with the mqueuefs in
which the file was created. So if a user doesn't remount mqueuefs after
unshare(CLONE_NEWIPC), mq_open("/ab") will not be reflected in "ls
/dev/mqueue".
If task a mounts mqueue for ipc_ns:1, then clones task b with a new ipcns,
ipcns:2, and then task a is the last task in ipc_ns:1 to exit, then (1)
ipc_ns:1 will be freed, (2) it's superblock will live on until task b
umounts the corresponding mqueuefs, and vfs actions will continue to
succeed, but (3) sb->s_fs_info will be NULL for the sb corresponding to
the deceased ipc_ns:1.
To make this happen, we must protect the ipc reference count when
a) a task exits and drops its ipcns->count, since it might be dropping
it to 0 and freeing the ipcns
b) a task accesses the ipcns through its mqueuefs interface, since it
bumps the ipcns refcount and might race with the last task in the ipcns
exiting.
So the kref is changed to an atomic_t so we can use
atomic_dec_and_lock(&ns->count,mq_lock), and every access to the ipcns
through ns = mqueuefs_sb->s_fs_info is protected by the same lock.
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-04-07 06:01:10 +04:00
# include <linux/fs.h>
# include <linux/mount.h>
2011-03-24 02:43:23 +03:00
# include <linux/user_namespace.h>
2010-03-08 05:48:39 +03:00
# include <linux/proc_fs.h>
2008-02-08 15:18:22 +03:00
# include "util.h"
2011-03-24 02:43:24 +03:00
static struct ipc_namespace * create_ipc_ns ( struct task_struct * tsk ,
struct ipc_namespace * old_ns )
2008-02-08 15:18:22 +03:00
{
struct ipc_namespace * ns ;
namespaces: ipc namespaces: implement support for posix msqueues
Implement multiple mounts of the mqueue file system, and link it to usage
of CLONE_NEWIPC.
Each ipc ns has a corresponding mqueuefs superblock. When a user does
clone(CLONE_NEWIPC) or unshare(CLONE_NEWIPC), the unshare will cause an
internal mount of a new mqueuefs sb linked to the new ipc ns.
When a user does 'mount -t mqueue mqueue /dev/mqueue', he mounts the
mqueuefs superblock.
Posix message queues can be worked with both through the mq_* system calls
(see mq_overview(7)), and through the VFS through the mqueue mount. Any
usage of mq_open() and friends will work with the acting task's ipc
namespace. Any actions through the VFS will work with the mqueuefs in
which the file was created. So if a user doesn't remount mqueuefs after
unshare(CLONE_NEWIPC), mq_open("/ab") will not be reflected in "ls
/dev/mqueue".
If task a mounts mqueue for ipc_ns:1, then clones task b with a new ipcns,
ipcns:2, and then task a is the last task in ipc_ns:1 to exit, then (1)
ipc_ns:1 will be freed, (2) it's superblock will live on until task b
umounts the corresponding mqueuefs, and vfs actions will continue to
succeed, but (3) sb->s_fs_info will be NULL for the sb corresponding to
the deceased ipc_ns:1.
To make this happen, we must protect the ipc reference count when
a) a task exits and drops its ipcns->count, since it might be dropping
it to 0 and freeing the ipcns
b) a task accesses the ipcns through its mqueuefs interface, since it
bumps the ipcns refcount and might race with the last task in the ipcns
exiting.
So the kref is changed to an atomic_t so we can use
atomic_dec_and_lock(&ns->count,mq_lock), and every access to the ipcns
through ns = mqueuefs_sb->s_fs_info is protected by the same lock.
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-04-07 06:01:10 +04:00
int err ;
2008-02-08 15:18:22 +03:00
ns = kmalloc ( sizeof ( struct ipc_namespace ) , GFP_KERNEL ) ;
if ( ns = = NULL )
2008-02-08 15:18:57 +03:00
return ERR_PTR ( - ENOMEM ) ;
2008-02-08 15:18:22 +03:00
namespaces: ipc namespaces: implement support for posix msqueues
Implement multiple mounts of the mqueue file system, and link it to usage
of CLONE_NEWIPC.
Each ipc ns has a corresponding mqueuefs superblock. When a user does
clone(CLONE_NEWIPC) or unshare(CLONE_NEWIPC), the unshare will cause an
internal mount of a new mqueuefs sb linked to the new ipc ns.
When a user does 'mount -t mqueue mqueue /dev/mqueue', he mounts the
mqueuefs superblock.
Posix message queues can be worked with both through the mq_* system calls
(see mq_overview(7)), and through the VFS through the mqueue mount. Any
usage of mq_open() and friends will work with the acting task's ipc
namespace. Any actions through the VFS will work with the mqueuefs in
which the file was created. So if a user doesn't remount mqueuefs after
unshare(CLONE_NEWIPC), mq_open("/ab") will not be reflected in "ls
/dev/mqueue".
If task a mounts mqueue for ipc_ns:1, then clones task b with a new ipcns,
ipcns:2, and then task a is the last task in ipc_ns:1 to exit, then (1)
ipc_ns:1 will be freed, (2) it's superblock will live on until task b
umounts the corresponding mqueuefs, and vfs actions will continue to
succeed, but (3) sb->s_fs_info will be NULL for the sb corresponding to
the deceased ipc_ns:1.
To make this happen, we must protect the ipc reference count when
a) a task exits and drops its ipcns->count, since it might be dropping
it to 0 and freeing the ipcns
b) a task accesses the ipcns through its mqueuefs interface, since it
bumps the ipcns refcount and might race with the last task in the ipcns
exiting.
So the kref is changed to an atomic_t so we can use
atomic_dec_and_lock(&ns->count,mq_lock), and every access to the ipcns
through ns = mqueuefs_sb->s_fs_info is protected by the same lock.
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-04-07 06:01:10 +04:00
atomic_set ( & ns - > count , 1 ) ;
err = mq_init_ns ( ns ) ;
if ( err ) {
kfree ( ns ) ;
return ERR_PTR ( err ) ;
}
2008-04-29 12:00:40 +04:00
atomic_inc ( & nr_ipc_ns ) ;
2008-02-08 15:18:57 +03:00
sem_init_ns ( ns ) ;
msg_init_ns ( ns ) ;
shm_init_ns ( ns ) ;
2008-02-08 15:18:22 +03:00
2008-04-29 12:00:44 +04:00
/*
* msgmni has already been computed for the new ipc ns .
* Thus , do the ipcns creation notification before registering that
* new ipcns in the chain .
*/
ipcns_notify ( IPCNS_CREATED ) ;
2008-04-29 12:00:42 +04:00
register_ipcns_notifier ( ns ) ;
2011-11-17 11:15:31 +04:00
ns - > user_ns = get_user_ns ( task_cred_xxx ( tsk , user_ns ) ) ;
2011-03-24 02:43:23 +03:00
2008-02-08 15:18:22 +03:00
return ns ;
}
2011-03-24 02:43:24 +03:00
struct ipc_namespace * copy_ipcs ( unsigned long flags ,
struct task_struct * tsk )
2008-02-08 15:18:22 +03:00
{
2011-03-24 02:43:24 +03:00
struct ipc_namespace * ns = tsk - > nsproxy - > ipc_ns ;
2008-02-08 15:18:22 +03:00
if ( ! ( flags & CLONE_NEWIPC ) )
2009-06-18 03:27:54 +04:00
return get_ipc_ns ( ns ) ;
2011-03-24 02:43:24 +03:00
return create_ipc_ns ( tsk , ns ) ;
2008-02-08 15:18:22 +03:00
}
2008-02-08 15:18:57 +03:00
/*
* free_ipcs - free all ipcs of one type
* @ ns : the namespace to remove the ipcs from
* @ ids : the table of ipcs to free
* @ free : the function called to free each individual ipc
*
* Called for each kind of ipc when an ipc_namespace exits .
*/
void free_ipcs ( struct ipc_namespace * ns , struct ipc_ids * ids ,
void ( * free ) ( struct ipc_namespace * , struct kern_ipc_perm * ) )
{
struct kern_ipc_perm * perm ;
int next_id ;
int total , in_use ;
down_write ( & ids - > rw_mutex ) ;
in_use = ids - > in_use ;
for ( total = 0 , next_id = 0 ; total < in_use ; next_id + + ) {
perm = idr_find ( & ids - > ipcs_idr , next_id ) ;
if ( perm = = NULL )
continue ;
ipc_lock_by_ptr ( perm ) ;
free ( ns , perm ) ;
total + + ;
}
up_write ( & ids - > rw_mutex ) ;
}
2009-06-18 03:27:56 +04:00
static void free_ipc_ns ( struct ipc_namespace * ns )
{
/*
* Unregistering the hotplug notifier at the beginning guarantees
* that the ipc namespace won ' t be freed while we are inside the
* callback routine . Since the blocking_notifier_chain_XXX routines
* hold a rw lock on the notifier list , unregister_ipcns_notifier ( )
* won ' t take the rw lock before blocking_notifier_call_chain ( ) has
* released the rd lock .
*/
unregister_ipcns_notifier ( ns ) ;
sem_exit_ns ( ns ) ;
msg_exit_ns ( ns ) ;
shm_exit_ns ( ns ) ;
atomic_dec ( & nr_ipc_ns ) ;
/*
* Do the ipcns removal notification after decrementing nr_ipc_ns in
* order to have a correct value when recomputing msgmni .
*/
ipcns_notify ( IPCNS_REMOVED ) ;
2011-03-24 02:43:23 +03:00
put_user_ns ( ns - > user_ns ) ;
2011-03-25 11:57:01 +03:00
kfree ( ns ) ;
2009-06-18 03:27:56 +04:00
}
namespaces: ipc namespaces: implement support for posix msqueues
Implement multiple mounts of the mqueue file system, and link it to usage
of CLONE_NEWIPC.
Each ipc ns has a corresponding mqueuefs superblock. When a user does
clone(CLONE_NEWIPC) or unshare(CLONE_NEWIPC), the unshare will cause an
internal mount of a new mqueuefs sb linked to the new ipc ns.
When a user does 'mount -t mqueue mqueue /dev/mqueue', he mounts the
mqueuefs superblock.
Posix message queues can be worked with both through the mq_* system calls
(see mq_overview(7)), and through the VFS through the mqueue mount. Any
usage of mq_open() and friends will work with the acting task's ipc
namespace. Any actions through the VFS will work with the mqueuefs in
which the file was created. So if a user doesn't remount mqueuefs after
unshare(CLONE_NEWIPC), mq_open("/ab") will not be reflected in "ls
/dev/mqueue".
If task a mounts mqueue for ipc_ns:1, then clones task b with a new ipcns,
ipcns:2, and then task a is the last task in ipc_ns:1 to exit, then (1)
ipc_ns:1 will be freed, (2) it's superblock will live on until task b
umounts the corresponding mqueuefs, and vfs actions will continue to
succeed, but (3) sb->s_fs_info will be NULL for the sb corresponding to
the deceased ipc_ns:1.
To make this happen, we must protect the ipc reference count when
a) a task exits and drops its ipcns->count, since it might be dropping
it to 0 and freeing the ipcns
b) a task accesses the ipcns through its mqueuefs interface, since it
bumps the ipcns refcount and might race with the last task in the ipcns
exiting.
So the kref is changed to an atomic_t so we can use
atomic_dec_and_lock(&ns->count,mq_lock), and every access to the ipcns
through ns = mqueuefs_sb->s_fs_info is protected by the same lock.
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-04-07 06:01:10 +04:00
/*
* put_ipc_ns - drop a reference to an ipc namespace .
* @ ns : the namespace to put
*
* If this is the last task in the namespace exiting , and
* it is dropping the refcount to 0 , then it can race with
* a task in another ipc namespace but in a mounts namespace
* which has this ipcns ' s mqueuefs mounted , doing some action
* with one of the mqueuefs files . That can raise the refcount .
* So dropping the refcount , and raising the refcount when
* accessing it through the VFS , are protected with mq_lock .
*
* ( Clearly , a task raising the refcount on its own ipc_ns
* needn ' t take mq_lock since it can ' t race with the last task
* in the ipcns exiting ) .
*/
void put_ipc_ns ( struct ipc_namespace * ns )
2008-02-08 15:18:22 +03:00
{
namespaces: ipc namespaces: implement support for posix msqueues
Implement multiple mounts of the mqueue file system, and link it to usage
of CLONE_NEWIPC.
Each ipc ns has a corresponding mqueuefs superblock. When a user does
clone(CLONE_NEWIPC) or unshare(CLONE_NEWIPC), the unshare will cause an
internal mount of a new mqueuefs sb linked to the new ipc ns.
When a user does 'mount -t mqueue mqueue /dev/mqueue', he mounts the
mqueuefs superblock.
Posix message queues can be worked with both through the mq_* system calls
(see mq_overview(7)), and through the VFS through the mqueue mount. Any
usage of mq_open() and friends will work with the acting task's ipc
namespace. Any actions through the VFS will work with the mqueuefs in
which the file was created. So if a user doesn't remount mqueuefs after
unshare(CLONE_NEWIPC), mq_open("/ab") will not be reflected in "ls
/dev/mqueue".
If task a mounts mqueue for ipc_ns:1, then clones task b with a new ipcns,
ipcns:2, and then task a is the last task in ipc_ns:1 to exit, then (1)
ipc_ns:1 will be freed, (2) it's superblock will live on until task b
umounts the corresponding mqueuefs, and vfs actions will continue to
succeed, but (3) sb->s_fs_info will be NULL for the sb corresponding to
the deceased ipc_ns:1.
To make this happen, we must protect the ipc reference count when
a) a task exits and drops its ipcns->count, since it might be dropping
it to 0 and freeing the ipcns
b) a task accesses the ipcns through its mqueuefs interface, since it
bumps the ipcns refcount and might race with the last task in the ipcns
exiting.
So the kref is changed to an atomic_t so we can use
atomic_dec_and_lock(&ns->count,mq_lock), and every access to the ipcns
through ns = mqueuefs_sb->s_fs_info is protected by the same lock.
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-04-07 06:01:10 +04:00
if ( atomic_dec_and_lock ( & ns - > count , & mq_lock ) ) {
mq_clear_sbinfo ( ns ) ;
spin_unlock ( & mq_lock ) ;
mq_put_mnt ( ns ) ;
free_ipc_ns ( ns ) ;
}
}
2010-03-08 05:48:39 +03:00
static void * ipcns_get ( struct task_struct * task )
{
struct ipc_namespace * ns = NULL ;
struct nsproxy * nsproxy ;
rcu_read_lock ( ) ;
nsproxy = task_nsproxy ( task ) ;
if ( nsproxy )
ns = get_ipc_ns ( nsproxy - > ipc_ns ) ;
rcu_read_unlock ( ) ;
return ns ;
}
static void ipcns_put ( void * ns )
{
return put_ipc_ns ( ns ) ;
}
2012-07-26 12:13:20 +04:00
static int ipcns_install ( struct nsproxy * nsproxy , void * new )
2010-03-08 05:48:39 +03:00
{
2012-07-26 12:13:20 +04:00
struct ipc_namespace * ns = new ;
if ( ! ns_capable ( ns - > user_ns , CAP_SYS_ADMIN ) )
return - EPERM ;
2010-03-08 05:48:39 +03:00
/* Ditch state from the old ipc namespace */
exit_sem ( current ) ;
put_ipc_ns ( nsproxy - > ipc_ns ) ;
nsproxy - > ipc_ns = get_ipc_ns ( ns ) ;
return 0 ;
}
const struct proc_ns_operations ipcns_operations = {
. name = " ipc " ,
. type = CLONE_NEWIPC ,
. get = ipcns_get ,
. put = ipcns_put ,
. install = ipcns_install ,
} ;