| lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87ha5h42va.fsf@x220.int.ebiederm.org> Date: Fri, 25 Apr 2014 12:37:29 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Andy Lutomirski <luto@...capital.net> Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>, "Serge E. Hallyn" <serge@...onical.com>, Linux Containers <containers@...ts.linux-foundation.org> Subject: Re: pid ns feature request Andy Lutomirski <luto@...capital.net> writes: > Unless I'm missing some trick, it's currently rather painful to mount > a namespace /proc. You have to actually be in the pid namespace to > mount the correct /proc instance, and you can't unmount the old /proc > until you've mounted the new /proc. This means that you have to fork > into the new pid namespace before you can finish setting it up. Yes. You have to be inside just about all namespaces before you can finish setting them up. I don't know the context in which needed to be inside the pid namespace is a burden. > Would it make sense to add a mount option to procfs to request a mount > for pid_ns_for_children instead of task_active_pid_ns? This is about the using setns and unshare? Adding a proc amount option that takes a pid namespace file descriptor would be the general solution, and might be worth implementing. Getting a pid namespace file descriptors when there are no pids might be a challenge. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists