mount namespace : who mounted what ?
in [Kernel]
|
Prev: x86: make save_stack_address() !CONFIG_FRAME_POINTER friendly
Next: [PATCH -v2] pci: clear bridge resource size if BIOS assign bad one
From: Daniel Lezcano on 3 Jun 2010 16:10 Hi all, I was wondering, in a new mount namespace, if it is possible to know which mount points were inherited and which were mounted in a new namespace ? I looked at /proc/<pid>/mountinfo and investigated a bit on the mount id, but this one is not reliable as it changes in the new namespace. The /proc/<pid>/mounts file shows all the mount points visible for the process inherited or not. Any ideas ? Thanks -- Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Al Viro on 4 Jun 2010 00:10 On Thu, Jun 03, 2010 at 10:04:13PM +0200, Daniel Lezcano wrote: > Hi all, > > I was wondering, in a new mount namespace, if it is possible to know > which mount points were inherited and which were mounted in a new > namespace ? > > I looked at /proc/<pid>/mountinfo and investigated a bit on the > mount id, but this one is not reliable as it changes in the new > namespace. The /proc/<pid>/mounts file shows all the mount points > visible for the process inherited or not. No more than "had it been this process that mmaped that area or was it inherited from the parent?" -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Daniel Lezcano on 4 Jun 2010 06:20
On 06/04/2010 06:01 AM, Al Viro wrote: > On Thu, Jun 03, 2010 at 10:04:13PM +0200, Daniel Lezcano wrote: > >> Hi all, >> >> I was wondering, in a new mount namespace, if it is possible to know >> which mount points were inherited and which were mounted in a new >> namespace ? >> >> I looked at /proc/<pid>/mountinfo and investigated a bit on the >> mount id, but this one is not reliable as it changes in the new >> namespace. The /proc/<pid>/mounts file shows all the mount points >> visible for the process inherited or not. >> > No more than "had it been this process that mmaped that area or was it > inherited from the parent?" > Ok, thanks. I thought it may be interessting to add this information in the procfs (eg. /proc/<pid>/mountprivate) but wrt your remark that should have no sense as, to be consistent, we should do the same for all kind of inherited resources. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |