Ram Pai wrote: > > the second patch made a /proc/propagation interface which had almost the > same fields, but also added fields to show the propagation type of the > mount as well as pointers to its peers and master depending on the type > of the mount. > > I think the consensus seems to have a new interface /proc/make-a-name > which extends the interface provided by /proc/mounts but provides the > propagation state of the mounts too as well as disambiguate bind mounts. > Which makes sense. > Why? It seems a lot cleaner to have all the information in the same place. It is highly unfriendly to userspace to have to gather information in a lot of places, plus it adds race conditions. It would be another matter if the format that we have now couldn't be extended, but we need those fields (well, except the two zeros, but who cares) *anyway*, so we might as well stick to the existing file, and reduce the total amount of code and clutter. > > BTW: what is the need for overmounted flag? Do you mean two vfsmounts > mounted on the same dentry on the ***same vfsmount*** ? > Maybe I'm not following the uses of your flags well enough to figure out if that information can already been deduced. -hpa - 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
