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: Fri, 27 Jul 2007 15:43:01 -0400	[thread overview]
Message-ID: <46AA4AC5.2050200@oracle.com> (raw)
In-Reply-To: <E1IEQ7q-0000qE-00@dorka.pomaz.szeredi.hu>

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

Miklos:

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.

Miklos Szeredi wrote:
> [please consider pruning the CC list if discussing some aspect, which
> doesn't concern all]
> 
> I've done an audit of all filesystems with regards to showing mount
> options in /proc/<pid>/mounts.  Unfortunately most of them show none
> or only a part of all accepted options (for details see list of
> filesystems at the end of the mail).
> 
> This is currently not a big problem, because mount(8) stores the given
> options in /etc/mtab.  However we want to get rid of mtab, and this
> requires, that the option showing be fixed up.
> 
> It would be easiest if this was done by the VFS instead of having to
> deal with it in filesystems.  However there are differences in how
> filesytems handle options during mount and remount, and it would be
> impossible to take this into account in all cases.
> 
> If you are CC-ed, and responsible for one of these filesystems, please
> take a moment to fully implement the ->show_options() method.  In most
> cases it should be an easy task.
> 
> If for some reason you are unable to do this, please let me know and
> I'll fix it up.
> 
> Here are some guidelines for showing options.  I'll also add these to
> Documentation/filesystems/vfs.txt
> 
> +   If a filesystem accepts mount options, it must define show_options()
> +   to show all the currently active options.  The rules are:
> +
> +     - options MUST be shown which are not default or their values differ
> +       from the default
> +
> +     - options MAY be shown which are enabled by default or have their
> +       default value
> +
> +   Options used only internally between a mount helper and the kernel
> +   (such as file descriptors), or which only have an effect during the
> +   mounting (such as ones controlling the creation of a journal) are exempt
> +   from the above rules.
> 
> Thanks,
> Miklos
> 
> -------
> legend:
> 
>   all - fs has options, but doesn't define ->show_options()
>   some - fs defines ->show_options(), but some options are not shown
>   noopt - fs does not have options
>   good - fs shows all options
>   patch - I have a patch
> 
> 
> 9p          some
> adfs        all (maintainer?)
> affs        all
> afs         all
> autofs      all
> autofs4     some
> befs        all
> bfs         noopt
> cifs        some (odd parser)
> coda        noopt
> configfs    noopt
> cramfs      noopt
> debugfs     noopt
> devpts      patch
> ecryptfs    some
> efs         noopt
> ext2        patch
> ext3        patch
> ext4        patch
> fat         some
> freevxfs    noopt
> fuse        patch
> gfs2        good
> hfs         good
> hfsplus     good
> hostfs      patch
> hpfs        all
> hppfs       noopt
> hugetlbfs   all
> isofs       all (maintainer?)
> jffs2       noopt
> jfs         some
> minix       noopt
> msdos       ->fat
> ncpfs       all (FS_BINARY_MOUNTDATA?)
> nfs         some
> nfsd        noopt
> ntfs        good (odd parser)
> ocfs2       all
> openpromfs  noopt
> proc        noopt
> qnx4        noopt
> ramfs       noopt
> reiserfs    all
> romfs       noopt
> smbfs       good (odd parser) (maintainer?)
> sysfs       noopt
> sysv        noopt
> udf         all
> ufs         all
> vfat        ->fat
> xfs         some (odd parser)
> 
> mm/shmem.c                                    patch
> drivers/oprofile/oprofilefs.c                 noopt
> drivers/infiniband/hw/ipath/ipath_fs.c        noopt
> drivers/misc/ibmasm/ibmasmfs.c                noopt
> drivers/usb/core (usbfs)                      noopt
> drivers/usb/gadget (gadgetfs)                 noopt
> drivers/isdn/capi/capifs.c                    noopt
> kernel/cpuset.c                               noopt
> fs/binfmt_misc.c                              noopt
> net/sunrpc/rpc_pipe.c                         noopt
> arch/powerpc/platforms/cell/spufs             all
> arch/s390/hypfs                               all
> ipc/mqueue.c                                  noopt
> security (securityfs)                         noopt
> security/selinux/selinuxfs.c                  noopt
> 
> in -mm:
> 
> reiser4                some (odd parser)
> kernel/container.c     good (odd parser)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 259 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
version:2.1
end:vcard


  parent reply	other threads:[~2007-07-27 19:46 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 [this message]
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
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=46AA4AC5.2050200@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