linux-kernel - mount --bind and /proc/mounts

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>] [day] [month] [year] [list]

Date:	Tue, 2 Jan 2007 14:55:32 +0100
From:	Mark Hlawatschek <hlawatschek@...x.de>
To:	linux-kernel@...r.kernel.org
Subject: mount --bind and /proc/mounts

Hi,

I'm using a shared root environment and therefore linked /etc/mtab 
to /proc/mounts. In addition I'm using --bind mount to make administration 
easier.

Now I found the following behaviour:
# mount -a 
is mounting all filesystems with bind options in the fstab 
everytime the command "mount -a " is executed. 

That works fine using an /etc/mtab file, but fails for --bind mounts 
using /etc/mtab linked to /proc/mounts.

I think this is because /etc/mtab has information about the source directory 
and /proc/mounts shows the device, hosting the filesystem.

e.g.
# mount --bind /tmp/bmount/ /mnt/bmount/
# cat /etc/mtab
(...) /tmp/bmount /mnt/bmount none rw,bind 0 0
# cat /proc/mounts
(...) /dev/root /mnt/bmount ext3 rw,data=ordered 0 0

Is there a solution for this ?

Thanks,

Mark

-
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/