public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Anoop Vijayan <acv@linux.vnet.ibm.com>
Cc: acl-devel@nongnu.org, xfs@oss.sgi.com
Subject: Re: getfacl gives octal output for Hebrew user/group names
Date: Wed, 17 Jun 2009 09:18:51 -0500	[thread overview]
Message-ID: <4A38FB4B.20002@sandeen.net> (raw)
In-Reply-To: <4A38F04C.9090909@linux.vnet.ibm.com>

Anoop Vijayan wrote:
> Hello!
> 
> Running RHEL5 U2 x86_64, with Samba & Winbind configure to work with Active-Directory env.
> Users & Groups in the Active-Directory are in hebrew and locale settings are correct (Hebrew/UTF-8)
> Posix Acls on file has special characters ('\' & hebrew chars) for the group/user names.
> In circumstances like this, where the user/group accounts come from an AD
> server, getfacl could be showing the "invalid" characters as octal.
> Example:

cc'ing back to the new acl list.

-Eric

> [root]# getfacl a.a
> # file: a.a
> # owner: GTS\134\327\236\327\225\327\251\327\225\327\237
> # group: root
> user::rw-
> group::r--
> group:GTS\134\327\251\327\236\327\225\327\250:-w-
> group:GTS\134\327\251\327\250\327\252:r-x
> mask::rwx
> other::r--
> 
> Now - we are also have GPFS fs and when we run the mmgetacl command the Posix
> acls in Hebrew showed OK.
> 
> I am trying to work out a patch which fixes this and the issue seems to be here
> const char *quote(const char *str)
> {
>      static char *quoted_str;
>      static size_t quoted_str_len;
>      const unsigned char *s;
>      char *q;
>      size_t nonpr;
> 
>      if (!str)
>          return str;
> 
>      for (nonpr = 0, s = (unsigned char *)str; *s != '\0'; s++)
>          if (!isprint(*s) || isspace(*s) || *s == '\\' || *s == '=') <========
>              nonpr++;
>      if (nonpr == 0)
>          return str;
> 
>      if (high_water_alloc((void **)&quoted_str, &quoted_str_len,
>                   (s - (unsigned char *)str) + nonpr * 3 + 1))
>          return NULL;
>      for (s = (unsigned char *)str, q = quoted_str; *s != '\0'; s++) {
>          if (!isprint(*s) || isspace(*s) || *s == '\\' || *s == '=') { <========
>              *q++ = '\\';
>              *q++ = '0' + ((*s >> 6)    );
>              *q++ = '0' + ((*s >> 3) & 7);
>              *q++ = '0' + ((*s     ) & 7);
>          } else
>              *q++ = *s;
>      }
> 
> Removing the checks isprint(*s) and *s == '\\' resolves the issue.
> AD shares are associated with a doamin name and AD users/groups will be in the format Dom\user.
> Can someone explain why these checks are required?
> 
> PS. Please include me in the reply as I have not subscribed to this list.
> 
> Cheers!
> - Anoop
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-06-17 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 13:31 getfacl gives octal output for Hebrew user/group names Anoop Vijayan
2009-06-17 14:18 ` Eric Sandeen [this message]
2009-06-19 17:17 ` Andreas Gruenbacher
2009-06-22  7:30   ` Anoop Vijayan
2009-06-23  9:48     ` [Acl-devel] " Andreas Gruenbacher

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=4A38FB4B.20002@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=acl-devel@nongnu.org \
    --cc=acv@linux.vnet.ibm.com \
    --cc=xfs@oss.sgi.com \
    /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