> On Tue, 2008-03-11 at 17:17 +0100, Miklos Szeredi wrote: > > [One more RFC for mountinfo, and then I'll really send them to > > Andrew.] > > > > Two changes: > > > > 1. Only show reachable mounts in /proc/<pid>/mountinfo, this makes > > mountpoints unambiguous for chrooted processes. > > > > 2. Instead of showing mountpoints relative to the current root, always > > show them relative to the queried task's root. > > > > This means, that a particular mountinfo file will always have the same > > contents, regardless of which process is reading the file. Which is a > > lot more consistent, than the current behavior of /proc/<pid>/mounts. > > > What about the propagation aspect? Won't you have to show only those > master mount pgid's that have a mounts within the same chrooted tree? You mean, the dominating mount's pgid? Yes, it would make sense to show only the one which is under the same root. I'm a bit sceptical about the worth of this dominating mount pgid thing, but Al thinks it's a good idea, so... About the immediate master's pgid, I think we decided, that it's not a problem to show it, even if there's no representative mount of it under the current namespace (or root). Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
