From: Karel Zak <kzak@redhat.com>
To: "Mantas Mikulėnas" <grawity@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: findmnt on 3.14-rc3 – only shows /proc in tree mode
Date: Thu, 20 Feb 2014 17:24:25 +0100 [thread overview]
Message-ID: <20140220162425.GB27495@x2.net.home> (raw)
In-Reply-To: <le50p4$1td$1@ger.gmane.org>
On Thu, Feb 20, 2014 at 03:43:13PM +0200, Mantas Mikulėnas wrote:
> Using util-linux 2.24.1 on Arch Linux, running `findmnt` only shows
> mounts at or under "/proc", and ignores all other mount points
> (including "/"). This only happens in "tree" mode – if I run `findmnt
> --raw` it lists all mounts correctly.
>
> This happens with custom-built 3.14-rc3 kernel, but works fine with
> Arch's stock 3.13.x (the same Arch initramfs for both). Building
> `findmnt` from util-linux.git did not change anything.
>
> > $ findmnt
> > TARGET SOURCE FSTYPE OPTIONS
> > /proc proc proc rw,nosuid,nodev,noexec,relatime
> > └─/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=21,pgrp=1,timeout=300,minprot
> > └─/proc/sys/fs/binfmt_misc binfmt_misc binfmt_mi rw,relatime
>
> It seems there is a small difference in /proc/self/mountinfo with 3.14;
> the entry for / looks like this:
>
> > 19 0 8:3 / / rw,relatime - ext4 /dev/sda3 rw,data=ordered
Hmm... it seems like the kernel does not have pseudo rootfs entry, so
the mount IDs starts from zero.
Fixed (commit 6c373810f5b1d32824371e9dff6ee5a006388f98),
it was bug in libmount mnt_table_get_root_fs().
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2014-02-20 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 13:43 findmnt on 3.14-rc3 – only shows /proc in tree mode Mantas Mikulėnas
2014-02-20 16:24 ` Karel Zak [this message]
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=20140220162425.GB27495@x2.net.home \
--to=kzak@redhat.com \
--cc=grawity@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.