linux-kernel - Re: [d_path 6/7] Filter out disconnected paths from /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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070420103429.72efe1dc@the-village.bc.nu>
Date:	Fri, 20 Apr 2007 10:34:29 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andreas Gruenbacher <agruen@...e.de>
Cc:	jjohansen@...e.de, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, chrisw@...s-sol.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [d_path 6/7] Filter out disconnected paths from /proc/mounts

> There is some disagreement what /proc/mounts should include. Currently it
> reports all mounts from the current namespace and doesn't include lazy
> unmounts. This leads to ambiguities with the rootfs (which is an internal mount
> irrelevant to user-space except in the initrd), and in chroots.
> 
> With this and the next patch, /proc/mounts only reports the mounts reachable
> for the current process, which makes a lot more sense IMO.  If the current
> process is rooted in the namespace root (which it usually is), it will see all
> mounts except for the rootfs.
> 
> Signed-off-by: Andreas Gruenbacher <agruen@...e.de>

This change in behaviour appears to be fine for glibc (except when trying
to find the name of a file from a namespace we are not in, which wouldn't
have come out right before either)

Acked-by: Alan Cox <alan@...hat.com>

(but still NAK on the getcwd change)
-
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/