From: Nathan Scott Subject: Re: xattr namespace question Date: Wed, 22 Mar 2006 10:58:28 +1100 Message-ID: <20060321235828.GB6846@frodo> References: <1142942773.6400.1212.camel@quoit.chygwyn.com> <20060321122119.GN6199@schatzie.adilger.int> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from omx2-ext.sgi.com ([192.48.171.19]:34760 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S1751849AbWCVACe (ORCPT ); Tue, 21 Mar 2006 19:02:34 -0500 To: Steven Whitehouse , a.gruenbacher@bestbits.at, linux-fsdevel@vger.kernel.org Content-Disposition: inline In-Reply-To: <20060321122119.GN6199@schatzie.adilger.int> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Mar 21, 2006 at 05:21:19AM -0700, Andreas Dilger wrote: > On Mar 21, 2006 12:06 +0000, Steven Whitehouse wrote: > > In order to remove the final ioctl() call in the GFS2 filesystem its > > been suggested that we use xattrs as a replacement interface. Mostly > > this is self-explanatory however there is one question that I've not > > been able to resolve 100% satisfactorily, which is what the namespace > > should look like. > > > > We have a bunch of boolean flags, so (using the example of the journaled > > data flag) should our xattrs be called something along the lines of "boolean flags" sounds alot more like the lsattr/chattr inode flags as Andreas points out. There is already a data journalling (j) flag there too. > > system.gfs2.jdata (this seems to be most popular suggestion amoung those > > I've asked privately), or perhaps system.fs.gfs2.jdata or indeed is the > > system namespace reserved for something special so that we should use a > > special gfs2 namespace instead? The choice typically depends on what the permissions model for access to the attribute needs to be. See attr(5). > If your extra flags can be mapped onto the EXT2_IOC_GETFLAGS equivalent, > then you may want to (also) consider that. This allows the flags to be > got/set by lsattr and chattr, respectively, and have been in linux for ages. > It also happens that ext2/ext3/reiserfs all share this same API. And XFS, and hfsplus too from the look of it. cheers. -- Nathan