public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Timothy Shimmin <tes@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] use generic_*xattr routines
Date: Mon, 26 May 2008 07:37:59 +0200	[thread overview]
Message-ID: <20080526053759.GA17825@lst.de> (raw)
In-Reply-To: <483A15CE.9060409@sgi.com>

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.

  reply	other threads:[~2008-05-26  5:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 11:22 [PATCH] use generic_*xattr routines Christoph Hellwig
2008-05-21  8:16 ` Christoph Hellwig
2008-05-22  7:17   ` Timothy Shimmin
2008-05-23  5:22   ` Timothy Shimmin
2008-05-23  5:48     ` Christoph Hellwig
2008-05-26  1:43       ` Timothy Shimmin
2008-05-26  5:37         ` Christoph Hellwig [this message]
2008-05-27 10:50           ` Timothy Shimmin
2008-05-29 12:39             ` Christoph Hellwig
2008-05-30  6:37               ` Timothy Shimmin
2008-05-30  7:53                 ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080526053759.GA17825@lst.de \
    --to=hch@lst.de \
    --cc=tes@sgi.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox