On Wed, Mar 25, 2009 at 07:36:45PM -0500, spencer shepler wrote: > On Wed, Mar 25, 2009 at 1:53 PM, Steve Dickson <SteveD@xxxxxxxxxx> wrote: > > Hello, > > > > What would be the ramifications of turning on the crossmnt > > option on by default? Currently the the default is nocrossmnt. > > > > In my recent work with pseudo exports, it has become very apparent > > that having the crossmnt always set, especially with multi file > > system exports, allows mount to "just work"! > > > > So historically what is the reason for not allowing the clients > > to always cross file systems? Is it a security issue? > > And again, what would be the ramifications always allowing, by > > default, clients to cross file systems? > > As Trond mentioned, the OpenSolaris client doesn't automatically > create mount points when crossing the server's filesystem boundaries > (for NFSv3). > NFSv4 support for that behavior is now present for OpenSolaris. > > So the risk is running into clients that don't behave like the Linux > client and then "mv" will not be able to determine the appropriate > behavior when mv'ing files between those filesystems. And some applications may be confused when they see different files that appear to be on the same filesystem but that have different inodes. Etc. And this requires people to change their exports. We've done this before (with sync and subtree_check), but it's something to avoid if at all possible. So preserving the current behavior for v2/v3 is important. --b. -- 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
