| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <E1IFnSa-0002BL-00@dorka.pomaz.szeredi.hu> Date: Tue, 31 Jul 2007 10:52:08 +0200 From: Miklos Szeredi <miklos@...redi.hu> To: chuck.lever@...cle.com CC: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, kzak@...hat.com, sfrench@...ba.org, trond.myklebust@....uio.no, mark.fasheh@...cle.com, kurt.hackel@...cle.com Subject: Re: request for patches: showing mount options > 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. Trond, do you have a roadmap for this? > I'm wondering if there are other such cases in other file systems. Anything that has /sbin/mount.XXX could be doing this. According to Karel, those are nfs, cifs and ocfs2. Miklos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists