netdev - Re: Persisting mounts between 'ip netns' invocations

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230929-paket-pechschwarz-a259da786431@brauner>
Date: Fri, 29 Sep 2023 11:25:21 +0200
From: Christian Brauner <brauner@...nel.org>
To: Nicolas Dichtel <nicolas.dichtel@...nd.com>
Cc: Toke Høiland-Jørgensen <toke@...hat.com>,
	netdev@...r.kernel.org, bpf@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	David Ahern <dsahern@...nel.org>
Subject: Re: Persisting mounts between 'ip netns' invocations

> I fear that creating a new mount ns for each net ns will introduce more problems.

Not sure if we're talking past each other but that is what's happening
now. Each new ip netns exec invocation will allocate a _new_ mount
namespace. In other words, if you have 300 ip netns exec commands
running then there will be 300 individual mount namespaces active.

What I tried to say is that ip netns exec could be changed to
_optionally_ allocate a prepared mount namespace that is shared between
ip netns exec commands. And yeah, that would need to be a new command
line addition to ip netns exec.