On Fri, 2010-07-09 at 08:33 +1000, James Morris wrote: > On Thu, 8 Jul 2010, David P. Quigley wrote: > > > > Otherwise, this is a global policy decision which affects all NFSv4 > > > mounts, right? > > > > > > > > > > I don't believe we have that ability in any other file system. > > NFS is quite different to other filesystems. Your files are on other > systems, for example, which may or may not support security labeling. And if that is the case then the capability flag does not get set in the NFSv4 server caps and we don't use security label support on that mount. > > > If you want to decide that you want to use genfs style labels on NFSv4 > > just use a context mount. > > So, we enable this feature, and virtually all existing mounts break > because the servers do not support labeling. No it should default back to being nfs_t which is what happens when I use my client on an export that doesn't have security_label set. > > > That way you can have the default behavior be > > use security label support unless you don't want to and then you can > > have a context mount. > > It needs to be the other way around. This is a new feature, so the > default needs to be the existing behavior, with security labeling as an > option to enable at mount time. We made sure it falls back properly. It was decided a long time ago with discussion by several people that having it default to use it if its there otherwise fall back to the old behavior makes much more sense to an administrator. > > > > - James -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
