On Wed, Jan 04, 2017 at 11:56:36AM -0500, bfields wrote: > This is something I should have noticed before merging labeled NFS: > labeled NFS shouldn't be on by default, among other reasons because it > assumes everybody's using consistent security policies. As 4.2 is > getting turned on by default, this is starting to generate bug reports. > > The patch below turns it off by default, and provides a new option to > turn it on per export. The drawback is a regression on kernel upgrade > for anyone depending on labeled NFS, until they find the new option. My > impression is that's a specialized use case that still has a small > number of users at this point, so I think we can get away with that. > > The below is untested. I have a (small) nfs-utils patch as well. OK, I've tested now, the only problem was actually a preexisting bug--I'll post the patches, plus the companion nfs-utils patch. --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
