xfs
[Top] [All Lists]

Re: [PATCH] use generic_*xattr routines

To: Timothy Shimmin <tes@xxxxxxx>
Subject: Re: [PATCH] use generic_*xattr routines
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 26 May 2008 07:37:59 +0200
Cc: xfs-oss <xfs@xxxxxxxxxxx>
In-reply-to: <483A15CE.9060409@xxxxxxx>
References: <20080430112217.GB16966@xxxxxx> <20080521081656.GA2638@xxxxxx> <48365486.3060503@xxxxxxx> <20080523054848.GA29507@xxxxxx> <483A15CE.9060409@xxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Mon, May 26, 2008 at 11:43:42AM +1000, Timothy Shimmin wrote:
> I guess this is done to some extent by the put_listent() callback.
> Though, the context structure is probably a bit overused in different
> ways.
> The callback was also used for searching (for parent-ptr code) as well
> as for list formatting.
> I presume we are preserving the valuelen list format to keep the API
> for xfs_attrlist_by_handle used by xfsdump and probably for dmf.

Yes, the idea is to change the put_listen callback for work more like
filldir.  Thas is:

 - the callback is supplied by the xfs_attr_list caller, not set based
   on options
 - there will be an opaque object supplied to xfs_attr_list that is to
   be used by put_listent so that we don't have to pass down
   implementation-specific arguments directly.

I'd also like to move the attrlist_cursor_kern_t into this callback
opaque context because it doesn't make sense for the normal xattr API,
but I'll have to see if that's actually feasible.


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