xfs
[Top] [All Lists]

Re: getfacl reports unknown error 524 on xfs partition

To: linux-xfs@xxxxxxxxxxx
Subject: Re: getfacl reports unknown error 524 on xfs partition
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Fri, 10 May 2002 05:43:37 -0800
In-reply-to: <Pine.LNX.4.44.0205100819060.13361-100000@xxxxxxxxxxxxxxxxxxxxxx>; from sandeen@xxxxxxx on Fri, May 10, 2002 at 08:26:11AM -0500
Mail-copies-to: nobody
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <20020510012102.K11075@xxxxxxxxxxxxxxx> <Pine.LNX.4.44.0205100819060.13361-100000@xxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Fri, May 10, 2002 at 08:26:11AM -0500, Eric Sandeen wrote:
> Ah, thanks Ethan!  Should have read your reply before I sent mine.  :)
> 
> Nathan made this change about 4 weeks ago to fs/xfs/linux/xfs_linux.h,
> I think it should address this problem?

ah i must have missed it, i assume he changed it to return EOPNOTSUPP
instead of ENOTSUP (like xattr.c does) ?  if so that should do it.
but im too lazy to compile a kernel without XFS acl support just to
see ;-)

> > ENOTSUP was defined to be ENOTSUPP.  this is a problem because some glibc
> > versions and some architectures do not grok this code (errno.h in the kernel
> > only defines this within __KERNEL__).  we now define it as EOPNOTSUPP which
> > will work everywhere and is the same thing we use for extended attributes
> > not available elsewhere in the kernel (ENOTSUP is the ACL not enabled code).

yeah sounds about right.

*NOTSUP* seems to be quite a inconsistent mess.. at least in linuxland..

> Thanks,

no problem.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgpysTK9xBc0N.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>