Re: bug with multiple mounts of filesystems in 2.6

From: Mike Waychison
Date: Mon Jul 26 2004 - 19:59:21 EST


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Trond Myklebust wrote:
> På må , 26/07/2004 klokka 17:33, skreiv Mike Waychison:
>
>
>>How is this any different than having two seperate nfs clients accessing
>>the same nfs export?
>
>
> It isn't, but why do you think that should be a reason for allowing it?
>
> By all means feel free to add "mount --bind -oro" capabilities, but it
> is neither useful nor is it necessary to break the NFS caching model in
> order to do so.
>

Agreed. The two problems are orthogonal. [1]

As an example where sharing the super_block is wrong (albeit probably
just an oversight) is that the protocols (udp vs tcp) are not compared
in nfs_compare_super. You could argue that the client fhandles should
be different though, I'm not sure..

Another 'bind mount extension' that would be nice to change at the
vfsmount level may be w/rsize, but that is probably a very intrusive
change for nfs and probably not possible. Thoughts?

[1] - I haven't tested mounting nfs ro, and then mounting nfs rw using
the bind extensions. Does nfs make any assumptions about the mount
being ro?

- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
http://www.sun.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBBahXdQs4kOxk3/MRAhTCAKCJGOaemEdeDrmtp/tG5Y6fHe+BTgCgkh8v
312wdekZsxms1ShJciogYRQ=
=7Hm7
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/