From: Karel Zak <kzak@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: viro@ZenIV.linux.org.uk, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
util-linux-ng@vger.kernel.org, linuxram@us.ibm.com,
viro@ftp.linux.org.uk, hch@infradead.org, a.p.zijlstra@chello.nl
Subject: Re: [patch] VFS: extend /proc/mounts
Date: Thu, 17 Jan 2008 11:34:38 +0100 [thread overview]
Message-ID: <20080117103438.GC6922@petra.dvoda.cz> (raw)
In-Reply-To: <E1JFQEN-0005zn-2N@pomaz-ex.szeredi.hu>
On Thu, Jan 17, 2008 at 09:36:11AM +0100, Miklos Szeredi wrote:
> > I'd suggest doing a new file that would *not* try to imitate /etc/mtab.
> > Another thing is, how much of propagation information do we want to
> > be exposed and what do we intend to do with it?
>
> I think the scheme devised by Ram is basically right. It shows the
> relationships (slave, peer) and the ID of a master/peer mount.
Yes. It also shows the full relationship between source and
destination for bind mounts. Now the /proc/mounts is useless:
# mount --bind /mnt/test /mnt/test2
# cat /proc/mounts | grep test
/dev/root /mnt/test2 ext3 rw,noatime,data=ordered 0 0
> > What do we want to *do* with the information about propagation?
>
> Just feedback about the state of the thing. It's very annoying, that
> after setting up propagation, it's impossible to check the result.
Exactly.
Karel
--
Karel Zak <kzak@redhat.com>
prev parent reply other threads:[~2008-01-17 10:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 22:12 Miklos Szeredi
2008-01-16 22:30 ` Andrew Morton
2008-01-16 23:15 ` Miklos Szeredi
2008-01-16 23:43 ` Karel Zak
2008-01-16 23:58 ` Jan Engelhardt
2008-01-17 0:09 ` Andrew Morton
2008-01-17 3:35 ` Al Viro
2008-01-17 0:33 ` Neil Brown
2008-01-17 1:17 ` Jan Engelhardt
2008-01-17 8:55 ` Miklos Szeredi
2008-01-17 15:36 ` Chuck Lever
2008-01-17 2:45 ` H. Peter Anvin
2008-01-17 3:33 ` Al Viro
2008-01-17 8:36 ` Miklos Szeredi
2008-01-17 10:34 ` 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=20080117103438.GC6922@petra.dvoda.cz \
--to=kzak@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=miklos@szeredi.hu \
--cc=util-linux-ng@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®