From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [RFC] obsoleting /etc/mtab Date: Thu, 31 May 2007 17:11:40 -0700 Message-ID: <465F643C.7090008@zytor.com> References: <465EFA91.6070705@zytor.com> <20070531230421.GI5473@petra.dvoda.cz> <1180654235.7084.32.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Karel Zak , Miklos Szeredi , util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Trond Myklebust Return-path: In-Reply-To: <1180654235.7084.32.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> Sender: util-linux-ng-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org Trond Myklebust wrote: >>>> >>> A lot of these could be fixed all at once by letting the filesystem tell >>> the VFS to retain the string passed to the original mount. That will >> Unfortunately, the original option string (from userspace) != real >> options (in kernel), see NFS. This bug should be fixed -- the kernel >> has to fully follow mount(2) or ends with EINVAL. > > Way ahead of you... See patches 6 and 7 on > > http://client.linux-nfs.org/Linux-2.6.x/2.6.22-rc3/ > NFS takes a binary option block anyway. However, that's the exception, not the rule. -hpa