> > The reason knfsd gave up on the utf8 tests was complaints from people with > > filesystems with non-utf8 encodings. Given a preexisting filesystem > neither > > knfsd nor probably Ganesha has any way to determine the encoding, so > > we're left just injecting unhelpful errors when we come across something > > that doesn't look like utf-8. Which just annoyed people with those > > filesystems, didn't really help anyone else, and changed behavior on > NFSv3- > > >NFSv4 upgrade. > > > > But maybe non-utf8 is less common now. On Fri, Jul 29, 2016 at 02:55:19PM -0700, Frank Filz wrote: > Hmm, I can see that point. It would be interesting to see if we could just > lump utf8 tests into all now... In our case we'd have to reintroduce some sort of utf8 enforcement in knfsd, or only test with filesystems that will do that for us. The cases where that would cause problems are probably rarer now, but I'm still not ready to do that. --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
