From: NeilBrown <neilb@suse.de>
To: Linda Walsh <lkml@tlinx.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: RFE?: why no 'bind' info in /proc/mounts?
Date: Fri, 1 Nov 2013 15:15:21 +1100 [thread overview]
Message-ID: <20131101151521.2fa0b434@notabene.brown> (raw)
In-Reply-To: <5272FE79.30801@tlinx.org>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
On Thu, 31 Oct 2013 18:06:01 -0700 Linda Walsh <lkml@tlinx.org> wrote:
>
> If I only mount 1 file (or a subdir) via "bind", it still shows the entire
> device being mounted on the "bound" directory.
>
> Is there anyway to get a bit more granularity as to *what* was
> bound on a name? (subdir/file..?)
Take a look in /proc/self/mountinfo. It contains more useful stuff about the
mount table which couldn't be put in /proc/mounts without breaking
compatibility.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-11-01 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 1:06 RFE?: why no 'bind' info in /proc/mounts? Linda Walsh
2013-11-01 4:15 ` NeilBrown [this message]
2013-11-01 8:49 ` Linda Walsh
2013-11-01 11:57 ` Karel Zak
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=20131101151521.2fa0b434@notabene.brown \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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