linux-kernel - Re: /proc/self/mounts in chroot vs lxc

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

Date:	Mon, 06 Feb 2012 07:33:28 +0100
From:	Harald Dunkel <harri@...ics.de>
To:	Michael Tokarev <mjt@....msk.ru>
CC:	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: /proc/self/mounts in chroot vs lxc

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/05/12 11:33, Michael Tokarev wrote:
> 
> But plain chroot does not create new namespace, the process inherits parent namespace, so there is no way to clean in up cleanly.
> 

If I do a chroot to /mnt, then there is no "/mnt" in /proc/self/mounts
within this environment. Instead I see yet another entry for '/'.
This certainly looks like something private.

Maybe it would be easier for everybody if /proc/mounts (without "/self")
could always show the "real" mount points at the top level? A bind mount
of /abc to /mnt/abc would appear as /mnt/abc in /proc/mounts at all levels.
I could live with that.

Regards

Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk8vdDQACgkQUTlbRTxpHjcQOgCfXwKqVu7mAFTDctvcs1YAMQCq
FIsAn2UHiL+TncraqQffzdecN0eMadJy
=huO6
-----END PGP SIGNATURE-----
--
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/