namespace: ensure clone_flags are always stored in an unsigned long
commit213dd266d48af90c1eec8688c1ff31aa34d21de2
authorEric W. Biederman <ebiederm@xmission.com>
Mon, 16 Jul 2007 06:41:15 +0000 (15 23:41 -0700)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Mon, 16 Jul 2007 16:05:48 +0000 (16 09:05 -0700)
tree2882f6e84d36421ebe2a6360cfe0c773bd9053bd
parente3a68e30d28dbc6981dfc3d6ceddbfa2f885fe4e
namespace: ensure clone_flags are always stored in an unsigned long

While working on unshare support for the network namespace I noticed we
were putting clone flags in an int.  Which is weird because the syscall
uses unsigned long and we at least need an unsigned to properly hold all of
the unshare flags.

So to make the code consistent, this patch updates the code to use
unsigned long instead of int for the clone flags in those places
where we get it wrong today.

Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Acked-by: Cedric Le Goater <clg@fr.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fs/namespace.c
include/linux/mnt_namespace.h
include/linux/nsproxy.h
include/linux/pid_namespace.h
include/linux/utsname.h
kernel/nsproxy.c
kernel/pid.c
kernel/utsname.c