From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Karel Zak <kzak@redhat.com>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: mount-2.12r-ggk.tar.gz
Date: Tue, 19 Jun 2007 17:28:18 +0200 [thread overview]
Message-ID: <20070619152818.GA16363@apps.cwi.nl> (raw)
In-Reply-To: <20070619141528.GS7226@petra.dvoda.cz>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 2361 bytes --]
On Tue, Jun 19, 2007 at 04:15:28PM +0200, Karel Zak wrote:
> We use GIT for development, the utils/util-linux-ng is for releases.
Aha - and there have not been any releases yet.
> > Anyway, Dirk Gerrits, René Gabriël and Peter Kooijmans sent me
I meant Dirk Gerrits, René Gabriëls and Peter Kooijmans, sorry
> > [By the way, this shared subtree stuff is a bit messy,
> > and impossible to support correctly by mount without help
> > from the kernel. So far the shared/slave/unbindable status
> > of mounts is not visible in /proc/mounts or /proc/$$/mountstats.
>
> Unfortunately, you're right.
>
> We need something like /proc/PID/mounts_propagation
> (see 2nd patch in):
> http://www.mail-archive.com/util-linux-ng@vger.kernel.org/msg00136.html
Hmm - mounts_new - very ugly. Reminds me of oldolduname and family.
I see that you followed up and said the right things.
> > The above mount makes a feeble attempt to record these flags
> > in /etc/mtab, but will fail in any nontrivial situation.]
>
> I don't think that mtab is a good place for this shared subtree
> stuff. The mtab needs to die.
Perhaps. Perhaps not.
On the one hand I think there is a place for arbitrary user-space info
about mounted filesystems. With information about who mounted, and at what time.
What the icon is that should represent this filesystem. What resources are
associated to this mount, and which program must do the cleanup. Etc.
Today there is not much user-space info, but there is some.
On the other hand, the fact that the namespace is per-process
complicates matters. There is no natural location for a per-process mtab.
But maybe the easy solution is just to leave that to the users by giving
mount(8) an option "-M mtabfile".
What is missing is a way for user space to find out what the actual
kernel situation is, and that makes /etc/mtab imperfect. The right
implementation of "mount" (without options, roughly "cat /proc/mounts")
would be for mount to ask the kernel about all existing mounts,
merge the user space type information found in /etc/mtab, and give the result
to the user. (And update mtab if necessary.)
For the filesystem we have readdir() and stat() to find out about
the file hierarchy. I would like readmounts() and statmount() to find out
about the tree of mounts and the flags of each mount. Without using /proc.
Andries
next prev parent reply other threads:[~2007-06-19 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 12:38 mount-2.12r-ggk.tar.gz Andries.Brouwer
2007-06-19 14:15 ` mount-2.12r-ggk.tar.gz Karel Zak
2007-06-19 15:28 ` Andries Brouwer [this message]
2007-06-19 18:51 ` mount-2.12r-ggk.tar.gz Karel Zak
2007-06-19 21:08 ` mount-2.12r-ggk.tar.gz Andries Brouwer
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=20070619152818.GA16363@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=kzak@redhat.com \
--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 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.