From: Ram Pai <linuxram@us.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, util-linux-ng@vger.kernel.org,
viro@ftp.linux.org.uk, hch@infradead.org, a.p.zijlstra@chello.nl
Subject: Re: [RFC][PATCH] VFS: create /proc/<pid>/mountinfo
Date: Mon, 21 Jan 2008 13:53:13 -0800 [thread overview]
Message-ID: <1200952394.2988.70.camel@ram.us.ibm.com> (raw)
In-Reply-To: <E1JH49E-0006d6-N9@pomaz-ex.szeredi.hu>
On Mon, 2008-01-21 at 22:25 +0100, Miklos Szeredi wrote:
> > You have removed the code that checked if the peer or
> > master mount was in the same namespace before reporting their
> > corresponding mount-ids. One downside of that approach is the
> > user will see an mount_id in the output with no corresponding
> > line to explain the details of the mount_id.
>
> Before the change, the peer and master ID's were basically randomly
> chosen from the peers, which means, it wasn't possible to always
> determine, that two mounts were peers, or that they were slaves to the
> same peer group.
>
> After the change, this is possible, since the peer ID will be the same
> for all mounts which are peers. This means, that even though the peer
> ID might be in a different namespace, it is possible to determine all
> peers within the same namespace by comparing their peer ID's.
I agree with your reasoning on the random id; showing a single
id avoids clutter. But my point is, why not show a
id for the master or peer residing in the same namespace?
Showing a id with no corresponding entry for that id, can be
intriguing.
If no master-mount exists in the same namespace then print -1
meaning "masked".
there is always atleast one peer-mount in a given namespace; so no
issue there.
> >
> > And reporting the mount-id of a mount is some other namespace
> > could subtly mean information-leak?
>
> I don't think the mount ID itself can be sensitive, it really doesn't
> contain any information, other than being an identifier.
>
> > One other comment I had received offline from Steve French was
> > that the patch did not consider the following case:
> >
> > "Have you thought about whether this could handle the case in which cifs mounts with
> > a relative path e.g. currently
> > mount -t cifs //server/share /mnt
> >
> > can not be distinguished from
> > mount -t cifs //server/share/subdirectory /mnt
> >
> > when you run the mount command (ie the cifs "prefixpath" in this case
> > "/subdirectory" is not displayed)"
>
> Why cifs not displaying '//server/share/subdirectory' as the source of
> the mount?
dont know. not tried it myself.
RP
>
> Miklos
next prev parent reply other threads:[~2008-01-21 21:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 11:05 [RFC][PATCH] VFS: create /proc/<pid>/mountinfo Miklos Szeredi
2008-01-20 5:41 ` H. Peter Anvin
2008-01-20 8:23 ` Miklos Szeredi
2008-01-23 13:49 ` Pavel Machek
2008-01-23 19:02 ` H. Peter Anvin
2008-01-23 19:32 ` Miklos Szeredi
2008-01-20 11:20 ` Jan Engelhardt
2008-01-20 12:20 ` Miklos Szeredi
2008-01-21 19:48 ` Ram Pai
2008-01-21 21:25 ` Miklos Szeredi
2008-01-21 21:53 ` Ram Pai [this message]
2008-01-21 22:09 ` Miklos Szeredi
2008-01-22 20:56 ` Serge E. Hallyn
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=1200952394.2988.70.camel@ram.us.ibm.com \
--to=linuxram@us.ibm.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=miklos@szeredi.hu \
--cc=util-linux-ng@vger.kernel.org \
--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