From: Steve Dickson <SteveD@redhat.com>
To: Jim Rees <rees@umich.edu>
Cc: Gregor Gruener <ggruner@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2.6.32-131.6.1.el6.x86_64] idmapd.c: deactivate the ASCII characters check
Date: Thu, 01 Mar 2012 10:22:30 -0500 [thread overview]
Message-ID: <4F4F9436.8090307@RedHat.com> (raw)
In-Reply-To: <20120229213838.GA1560@umich.edu>
Hey,
On 02/29/2012 04:38 PM, Jim Rees wrote:
> Steve Dickson wrote:
>
> On 02/23/2012 04:16 AM, Gregor Gruener wrote:
> > Customers are using Unicode characters umlauts (ö,ä,ü) in group names and this
> > creates problems with NFS ID Mapping. Groups with umlauts will be redirected to
> > the group NFS "nobody".
> > This patch deactivate the ASCII characters check. It's maybe more like a temporary fix and I think it would be nicer to
> > adjust the check to support Unicode characters instead to deactivate the check.
> > Signed-off-by: Gregor Gruener<ggruner@redhat.com>
> ...
> Committed...
>
> I still think the name should be changed. The only thing validateascii() is
> doing now is verifying that the string is null terminated.
Sorry Jim... I kinda overlooked that part of the discussion...
I guess validateascii() is not a published interface so we
could change it... any suggestions? (Patches always welcome! ;-) )
steved.
next prev parent reply other threads:[~2012-03-01 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 9:16 [PATCH 2.6.32-131.6.1.el6.x86_64] idmapd.c: deactivate the ASCII characters check Gregor Gruener
2012-02-23 13:02 ` Jim Rees
2012-02-28 19:55 ` J. Bruce Fields
2012-02-29 20:48 ` Steve Dickson
2012-02-29 21:38 ` Jim Rees
2012-03-01 15:22 ` Steve Dickson [this message]
2012-05-17 17:40 ` Sorin Faibish
2012-05-17 17:43 ` pNFS block performance evaluation (sorry for the wrong subject title) Sorin Faibish
2012-05-18 9:37 ` tao.peng
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=4F4F9436.8090307@RedHat.com \
--to=steved@redhat.com \
--cc=ggruner@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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).