public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, kzak@redhat.com, ericvh@gmail.com,
	lucho@ionkov.net, zippel@linux-m68k.org, hpa@zytor.com,
	raven@themaw.net, rathamahata@php4.ru, dhowells@redhat.com,
	sfrench@samba.org, mhalcrow@us.ibm.com,
	phillip@hellewell.homeip.net, hirofumi@mail.parknet.co.jp,
	mikulas@artax.karlin.mff.cuni.cz, wli@holomorphy.com,
	shaggy@austin.ibm.com, vandrove@vc.cvut.cz,
	trond.myklebust@fys.uio.no, aia21@cantab.net,
	mark.fasheh@oracle.com, kurt.hackel@oracle.com,
	reiserfs-devel@vger.kernel.org, bfennema@falcon.csc.calpoly.edu,
	dushistov@mail.ru, xfs-masters@oss.sgi.com, arnd@arndb.de,
	holzheu@de.ibm.com
Subject: Re: request for patches: showing mount options
Date: Mon, 30 Jul 2007 11:20:34 -0400	[thread overview]
Message-ID: <46AE01C2.3000008@oracle.com> (raw)
In-Reply-To: <E1IEezF-0002g6-00@dorka.pomaz.szeredi.hu>

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]



Miklos Szeredi wrote:
>>>> Some mount options are never passed to the kernel, and thus can't appear 
>>>> in /proc/mounts.  Examples include user, users, and _netdev for NFS.
>>> These options control *who* may mount and *when* to mount.  They are
>>> not a property of the mount itself and are not added to /etc/mtab.
>>>
>>> There's a "user=ID" option that is added to /etc/mtab in case of user
>>> mounts.  This identifies the owner of the mount, so that it can be
>>> unmounted by that user.  There are patches in -mm that enable the
>>> kernel to store this info.
>>>
>>> Do you have other examples in mind?

There are a few more cases for NFS mount.

After a successful mount, the NFS mount command tucks some options into 
/etc/mtab that reflect which mountd was used for the mount, and what 
protocol version and port was used for the mount request.  Those options 
are not passed to the kernel, and do not appear in /proc/mounts today. 
See nfs(5)'s discussion of the mountport, mounthost, mountprog, and 
mountvers options.

However, the trend for NFS is to push mount option parsing into the 
kernel.  Thus all options will be passed to the kernel, and at that 
point it should be able to reflect the mount* options in /proc/mounts. 
But it doesn't do that quite yet.

I'm wondering if there are other such cases in other file systems.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


  reply	other threads:[~2007-07-30 15:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 13:45 request for patches: showing mount options Miklos Szeredi
2007-07-27 14:10 ` Steve French
2007-07-27 14:20   ` Miklos Szeredi
2007-07-27 15:30 ` Ian Kent
2007-07-27 15:40   ` Miklos Szeredi
2007-07-27 16:04     ` Steve French
2007-07-27 16:09       ` Miklos Szeredi
2007-07-28  6:45     ` Ian Kent
2007-07-29 15:07       ` Jan Engelhardt
2007-07-27 19:43 ` Chuck Lever
2007-07-27 20:03   ` Miklos Szeredi
2007-07-27 20:12     ` Chuck Lever
2007-07-28  5:37       ` Miklos Szeredi
2007-07-30 15:20         ` Chuck Lever [this message]
2007-07-31  8:52           ` Miklos Szeredi
2007-07-31 14:19             ` Chuck Lever
2007-07-31 20:22               ` Miklos Szeredi
2007-07-31 21:16                 ` Chuck Lever
2007-07-31 21:27                   ` Trond Myklebust
2007-08-01  6:20                     ` Miklos Szeredi
2007-07-31 22:21               ` Karel Zak
2007-08-01  6:52                 ` Miklos Szeredi

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=46AE01C2.3000008@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=aia21@cantab.net \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bfennema@falcon.csc.calpoly.edu \
    --cc=dhowells@redhat.com \
    --cc=dushistov@mail.ru \
    --cc=ericvh@gmail.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=holzheu@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=kurt.hackel@oracle.com \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=mark.fasheh@oracle.com \
    --cc=mhalcrow@us.ibm.com \
    --cc=miklos@szeredi.hu \
    --cc=mikulas@artax.karlin.mff.cuni.cz \
    --cc=phillip@hellewell.homeip.net \
    --cc=rathamahata@php4.ru \
    --cc=raven@themaw.net \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=sfrench@samba.org \
    --cc=shaggy@austin.ibm.com \
    --cc=trond.myklebust@fys.uio.no \
    --cc=vandrove@vc.cvut.cz \
    --cc=wli@holomorphy.com \
    --cc=xfs-masters@oss.sgi.com \
    --cc=zippel@linux-m68k.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