On Apr 25, 2008, at 10:35 AM, Steinar H. Gunderson wrote:
On Fri, Apr 25, 2008 at 10:30:35AM -0400, Chuck Lever wrote:
It's not exactly clear what the "sloppy" option is supposed to allow.
We are trying to figure out right now precisely how this should work.
Well, in general it seems to ignore any new options that come into
it. The
problem in question was -o grpid= that was coming in through autofs
mounts and was not too easy to remove for the user.
The grpid mount option is what triggered our earlier discussion of --
sloppy as well.
An expedient solution may be to tell the kernel mount option parser
specifically to ignore these common automounter options, like grpid.
Jeff, what do you think of that?
But before complaining too loudly about text-based mounts, please
remember that there was no specification for the mount.nfs command
and
mount system call interface except for a 15 year old man page. We
had
to do something to move forward with IPv6 and RDMA transports; the
legacy binary-only interface was simply inadequate.
Yes, I'm fully aware of that. (In particular, I'm waiting eagerly
for IPv6;
RDMA is a bit out of my range still. :-) ) People seem to depend on
a lot of
options behaving in a specific way, though.
Understood. Having neither a specification, a unit test suite, nor
any strong sense of history on the mailing list (ie not having a grip
on most use cases) means we are shooting blind in this case.
There will be some pain.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
