xfs
[Top] [All Lists]

Re: XFS/setfacl ordering bug still? - I think I Fixed ---- I think :) -

To: Eric Peters <eric@xxxxxxxxxx>
Subject: Re: XFS/setfacl ordering bug still? - I think I Fixed ---- I think :) - "patch" included
From: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 27 Aug 2001 11:17:35 +1100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <01e501c12ded$29585b40$020144c0@windows>; from eric@peters.org on Sat, Aug 25, 2001 at 10:08:28PM -0700
References: <200108242055.f7OKtIp06801@xenon.niehs.nih.gov> <3B86C267.8E4C951F@sgi.com> <01b201c12d90$72e9f3c0$020144c0@windows> <01e501c12ded$29585b40$020144c0@windows>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
hi,

On Sat, Aug 25, 2001 at 10:08:28PM -0700, Eric Peters wrote:
> After doing some gdb work and crap and downloading hte original setfacl port
> from http://acl.bestbits.at I noticed the acl_check function wasn't allowing
> more than one ACL_USER entry so:
> 
> libacl.c line 73:
>                 case ACL_USER:
>                         if (state != ACL_USER)
>                                 FAIL_CHECK (ACL_MISS_ERROR);
>                         if (ace->ae_id < qual || ace->ae_id ==
> ACL_UNDEFINED_ID)
>                                 FAIL_CHECK (ACL_DUPLICATE_ERROR);
>                         qual = ace->ae_id + 1;

> should become:
>                 case ACL_USER:
>                         if (state != ACL_USER)
>                                 FAIL_CHECK (ACL_MISS_ERROR);
>                         if (ace->ae_id < qual || ace->ae_id ==
> ACL_UNDEFINED_ID)
>                                 FAIL_CHECK (ACL_DUPLICATE_ERROR);
>                         qual = ace->ae_id + 1;
>                         needs_mask = 1;
>                         break;
> 

yup, thats clearly a bug.  fixed, thanks.

cheers.

-- 
Nathan


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