From: bfields@fieldses.org (J. Bruce Fields)
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: "'J. Bruce Fields'" <bfields@redhat.com>,
"'Linux NFS Mailing List'" <linux-nfs@vger.kernel.org>
Subject: Re: pynfs pull request
Date: Mon, 1 Aug 2016 10:42:56 -0400 [thread overview]
Message-ID: <20160801144256.GB4953@fieldses.org> (raw)
In-Reply-To: <047b01d1e9e3$e6d51fb0$b47f5f10$@mindspring.com>
> > 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.
next prev parent reply other threads:[~2016-08-01 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <037201d1e81e$04a9b9f0$0dfd2dd0$@mindspring.com>
[not found] ` <20160728193855.GF4732@pad>
2016-07-28 21:09 ` pynfs pull request Frank Filz
2016-07-29 21:30 ` J. Bruce Fields
2016-07-29 21:55 ` Frank Filz
2016-08-01 14:42 ` J. Bruce Fields [this message]
2016-10-21 15:53 ` J. Bruce Fields
2016-10-24 18:02 ` Frank Filz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160801144256.GB4953@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=ffilzlnx@mindspring.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).