LWN: Comments on "Mount namespaces, mount propagation, and unbindable mounts" https://lwn.net/Articles/690679/ This is a special feed containing comments posted to the individual LWN article titled "Mount namespaces, mount propagation, and unbindable mounts". en-us Wed, 15 Oct 2025 01:32:46 +0000 Wed, 15 Oct 2025 01:32:46 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Mount namespaces, mount propagation, and unbindable mounts https://lwn.net/Articles/716607/ https://lwn.net/Articles/716607/ cortana <div class="FormattedComment"> In one terminal:<br> <p> $ mkdir /tmp/foo<br> $ cd /tmp/foo<br> $ touch bar<br> $ ls<br> <p> In a second terminal:<br> <p> # mount --bind /etc /tmp/foo<br> <p> In the first terminal, you are still able to interact with the underlying /tmp/foo directory and its contents. Only once you cd out of the mount point does they become inaccessible.<br> <p> I think you are seeing the same behaviour when you try to mount something over the root directory.<br> </div> Thu, 09 Mar 2017 10:33:07 +0000 Mount namespaces, mount propagation, and unbindable mounts https://lwn.net/Articles/716577/ https://lwn.net/Articles/716577/ prabhunath <div class="FormattedComment"> # mount --bind / /opt/lxc <br> The above command will work, where the contents of / is visible in /opt/lxc<br> <p> # mount --bind /opt/lxc /<br> This will not work. Any reason for this ? Neither this command fails nor the contents of /opt/lxc is visible in /<br> </div> Thu, 09 Mar 2017 05:04:24 +0000