From: Karel Zak <kzak@redhat.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: util-linux@vger.kernel.org
Subject: Re: Mount -a and bind mounts. Bug?
Date: Fri, 9 Dec 2011 14:03:05 +0100 [thread overview]
Message-ID: <20111209130305.GD7960@nb.net.home> (raw)
In-Reply-To: <20111209130128.GC7960@nb.net.home>
On Fri, Dec 09, 2011 at 02:01:28PM +0100, Karel Zak wrote:
> On Fri, Dec 09, 2011 at 12:55:37PM +0000, Andrew Walrond wrote:
> > On Fri, Dec 09, 2011 at 01:48:37PM +0100, Karel Zak wrote:
> > > - distro?
> >
> > A custom job of my own
> >
> > > - linked with libmount?
> >
> > Don't think so.
> >
> > $ ldd /bin/mount
> > linux-vdso.so.1 => (0x00007fff093af000)
> > libblkid.so.1 => //lib/libblkid.so.1 (0x00007f087b755000)
> > libuuid.so.1 => //lib/libuuid.so.1 (0x00007f087b551000)
> > libc.so.6 => //lib/libc.so.6 (0x00007f087b1ca000)
> > /lib64/ld-linux-x86-64.so.2 => //lib64/ld-linux-x86-64.so.2 (0x00007f087b97b000)
> >
> > Saw some mention of libmount somewhere when I upgraded and built 2.20.1 but didn't have time to read further.
> > What's the current recommendation? Should I link against it?
> >
> > > - do you have regular mtab or symlink to /proc/mounts
> >
> > symlink to /proc/mounts
>
> ... okay then it's expected behavior. The file /proc/mounts does not
> provide enough information about bind mounts. You need regular mtab
> or link with libmount (the library reads /proc/self/mountinfo and
> does some horrible voodoo to detect already mounted bind mounts).
see also:
http://karelzak.blogspot.com/2011/04/bind-mounts-mtab-and-read-only.html
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-12-09 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 12:33 Mount -a and bind mounts. Bug? Andrew Walrond
2011-12-09 12:48 ` Karel Zak
2011-12-09 12:55 ` Andrew Walrond
2011-12-09 13:01 ` Karel Zak
2011-12-09 13:03 ` Karel Zak [this message]
2011-12-09 13:15 ` Andrew Walrond
2011-12-09 12:50 ` Andrew Walrond
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=20111209130305.GD7960@nb.net.home \
--to=kzak@redhat.com \
--cc=andrew@walrond.org \
--cc=util-linux@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