mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: GFS2 Filesystem [9/16]
Date: Mon, 27 Feb 2006 08:21:55 +0000	[thread overview]
Message-ID: <1141028515.6400.763.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602241559460.8198@excalibur.intercode>

Hi,

On Fri, 2006-02-24 at 16:05 -0500, James Morris wrote:
> On Fri, 24 Feb 2006, Steven Whitehouse wrote:
> 
> 
> > +/**
> > + * gfs2_ea_name2type - get the type of the ea, and truncate type from the name
> > + * @namep: ea name, possibly with type appended
> > + *
> > + * Returns: GFS2_EATYPE_XXX
> > + */
> > +
> > +unsigned int gfs2_ea_name2type(const char *name, char **truncated_name)
> > +{
> > +	unsigned int type;
> > +
> > +	if (strncmp(name, "system.", 7) == 0) {
> > +		type = GFS2_EATYPE_SYS;
> > +		if (truncated_name)
> > +			*truncated_name = strchr(name, '.') + 1;
> > +	} else if (strncmp(name, "user.", 5) == 0) {
> > +		type = GFS2_EATYPE_USR;
> > +		if (truncated_name)
> > +			*truncated_name = strchr(name, '.') + 1;
> > +	} else {
> > +		type = GFS2_EATYPE_UNUSED;
> > +		if (truncated_name)
> > +			*truncated_name = NULL;
> > +	}
> > +
> > +	return type;
> > +}
> 
> 
> Consider using the generic xattr infrastructure in the kernel (xattr.c), 
> e.g. generic_getxattr() and friends.
> 
> 
> 
> - James

Yes, I've also had some similar feedback in private email. We will
certainly look into doing this at the same time as we look at the
selinux/xattr support so its high on our agenda now. Thanks for the
feedback,

Steve.



      reply	other threads:[~2006-02-27  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 15:01 Steven Whitehouse
2006-02-24 21:05 ` James Morris
2006-02-27  8:21   ` Steven Whitehouse [this message]

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=1141028515.6400.763.camel@quoit.chygwyn.com \
    --to=swhiteho@redhat.com \
    --cc=akpm@osdl.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®