From: Al Viro <viro@ZenIV.linux.org.uk>
To: Daniel Lezcano <daniel.lezcano@free.fr>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mount namespace : who mounted what ?
Date: Fri, 4 Jun 2010 05:01:58 +0100 [thread overview]
Message-ID: <20100604040158.GZ31073@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4C080ABD.5040902@free.fr>
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?"
next prev parent reply other threads:[~2010-06-04 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 20:04 mount namespace : who mounted what ? Daniel Lezcano
2010-06-04 4:01 ` Al Viro [this message]
2010-06-04 10:14 ` Daniel Lezcano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100604040158.GZ31073@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=daniel.lezcano@free.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox