lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:	Sun, 28 Apr 2013 19:05:57 +0200
From:	richard -rw- weinberger <>
To:	linux-fsdevel <>,
	LKML <>,
	"Eric W. Biederman" <>
Subject: Modifying an existing mount namespace where user_ns != mnt_ns->user_ns


If I create a process with CLONE_NEWNS|CLONE_NEWUSER set, how can I
modify the mount namespace later?

I thought I simply can run setns(/proc/<child>/ns/mnt) within my
privileged process which resists in the initial userns and then mount
whatever I want into the child's mount namespace.
But this fails because do_new_mount() uses current->nsproxy->mnt_ns->user_ns.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists