linux-kernel - Re: Bind mount bug?

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]

Date:	Sun, 11 Nov 2007 23:29:16 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Roland Kuhn <rkuhn@....physik.tu-muenchen.de>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Frans Pop <elendil@...net.nl>
Subject: Re: Bind mount bug?


>> I'm not sure whether this is a bug or expected behavior.
>> Suppose I create a "looped" bind mount situation as follows.
>>
>> # mkdir test
>> # touch test/foo
>> # mkdir bindtest
>> # touch bindtest/bar
>> # mkdir bindtest/test
>> # mount --bind test/ bindtest/test/
>> # ls bindtest/test/
>> foo
>> # mount --bind bindtest/ test/
>
>This mounts the bindtest/ tree on test/ _without_ copying the mount  
>points which are found on subtrees. This is necessary to avoid loops  
>in the filesystem (bind mounts are somewhat like hardlinks on  
>directories, just without the headaches).

What you seek is mount --rbind.
-
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/