xfs
[Top] [All Lists]

Re: [NEWS] Extended attributes interface changes

To: Ethan Benson <erbenson@xxxxxxxxxx>
Subject: Re: [NEWS] Extended attributes interface changes
From: Nathan Scott <nathans@xxxxxxx>
Date: Sun, 3 Feb 2002 12:57:39 +1100
Cc: Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx>
In-reply-to: <20020201213849.Y14742@xxxxxxxxxxxxxxx>; from erbenson@xxxxxxxxxx on Fri, Feb 01, 2002 at 09:38:49PM -0900
References: <20020201101545.G88469@xxxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.44.0202021151090.5765-100000@xxxxxxxxxxxxxxxxxxxxxxxxx> <20020201213849.Y14742@xxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Fri, Feb 01, 2002 at 09:38:49PM -0900, Ethan Benson wrote:
> On Sat, Feb 02, 2002 at 11:52:38AM +0800, Federico Sevilla III wrote:
> > On Fri, 1 Feb 2002 at 10:15, Nathan Scott wrote:
> > > Yes, the ondisk formats remain unchanged, incl. the ondisk ACL format
> > > (which is also the same as the IRIX/XFS Posix ACL format).
> > 
> > So setups utilizing ACLs won't have to be redone, right? As long as we
> > make sure that when we upgrade to an XFS-enabled kernel using the new
> > system calls we also upgrade the userland stuff or we won't be able to
> > modify or view the ACL rules. Did I get things correctly? :)
> 
> for XFS at least yes.  on disk format is unchanged, only the syscalls
> are different.
> 
> however it looks like only the extended attributes syscalls have been
> added to 2.5, there is still no ACL interface.  I assume that the ACL
> userspace will have to change a second time when that API is accepted
> into the mainline kernel?  has the ACL api been more or less agreed on yet?
> 

We will be moving to the acl.bestbits.at implementation of
ACLs which uses the extended attributes interfaces directly
for ACLs, rather than separate syscalls as we have currently
in the XFS tree.

So, there will be no second change for ACL userspace, it will
all be done in one big step.

cheers.

-- 
Nathan


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