All of lore.kernel.org
 help / color / mirror / Atom feed
From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: James Morris <jmorris@namei.org>, selinux@tycho.nsa.gov
Subject: Re: [PATCH] XATTR issues on JFFS2
Date: Tue, 23 Aug 2005 22:35:11 +0900	[thread overview]
Message-ID: <430B260F.1070007@ak.jp.nec.com> (raw)
In-Reply-To: <1124800206.7874.17.camel@moss-spartans.epoch.ncsc.mil>

Hello,

Thanks for your comments.

The original reason not to use generic XATTR methods is that {get|set|list}_xattr
methods are called with XATTR-name which prefix is omitted.
e.g, sys_getxattr("security.selinux", ...)
      -> generic_getxattr("security.selinux", ...)
        -> jffs2_security_getxattr("selinux", ...)
                                    ~~~~~~~<- "security." was omitted.
In my implementation, the full-name is used to identify XATTR-entry.

But I noticed that we can use a combination of integer index number
(such as EXT2_XATTR_INDEX_SECURITY) and omitted XATTR-name for
the replacement of full-XATTR-name, and can use generic_xxxx().

I'll modify it in "take-2" patch.
(Why didn't I notice before posting...)

> Thanks for working on this functionality.  From a very brief look at the
> patch, one question I had was whether you could be using the generic
> xattr methods introduced by James Morris' earlier xattr code
> consolidation patches that are now in the mainline kernel.  See the
> generic_* functions in fs/xattr.c and how they are used by the fs code
> (e.g. look at the ext3 xattr implementation).  Per recent discussions on
> linux-fsdevel, using those helpers is the preferred approach for the
> future.  You can then just set sb->s_xattr for the specific handlers in
> jffs2, e.g. see the ext3 code for an example.

Thanks for this information. I'll contact to him before ACL implementation.

> Might be worth mentioning this work on acl-devel as well, although you
> don't yet support ACLs or other xattrs.  But I'm sure Andreas
> Gruenbacher would be interested, as he did the original xattr and ACL
> development work for ext[23], and he may be able to give feedback on
> your approach to various aspects like the attribute caching.
-- 
KaiGai Kohei <kaigai@kaigai.gr.jp>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-08-23 13:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 10:24 [PATCH] XATTR issues on JFFS2 Kaigai Kohei
2005-08-23 12:00 ` KaiGai Kohei
2005-08-23 12:30   ` Stephen Smalley
2005-08-23 13:35     ` KaiGai Kohei [this message]
2005-08-23 13:44       ` Stephen Smalley
2005-08-23 12:46 ` Jörn Engel
2005-08-23 12:52   ` David Woodhouse
2005-08-24  9:49     ` Kaigai Kohei
2005-08-25 10:28       ` Kaigai Kohei
2005-08-25 14:12         ` Jörn Engel
2005-09-07  5:14       ` Kaigai Kohei
2005-09-08 19:49         ` Jörn Engel
2005-09-08 19:54           ` David Woodhouse
2005-09-09  4:15           ` Kaigai Kohei
2005-09-09  7:24             ` Jörn Engel
2005-09-10  4:15               ` KaiGai Kohei
2005-09-11 11:46                 ` Jörn Engel
2005-09-12  2:17                   ` Kaigai Kohei
2005-09-12  6:40                     ` Jörn Engel
2005-09-12 11:01                       ` Kaigai Kohei
2005-09-28  8:44                         ` Kaigai Kohei
2005-09-29  7:45                           ` Jörn Engel
2005-10-03  1:01                             ` E-mail with attached file has not delivered yet. (Re: [PATCH] XATTR issues on JFFS2) Kaigai Kohei
2005-10-19 13:18                             ` [PATCH] XATTR issues on JFFS2 Kaigai Kohei
2005-10-19 14:24                               ` Jörn Engel
2005-10-20  2:01                                 ` Kaigai Kohei
2005-11-27  6:58                                 ` KaiGai Kohei
2005-11-27  9:43                                   ` KaiGai Kohei
2005-11-27 15:45                                     ` Artem B. Bityutskiy
2005-11-28  4:13                                       ` Kaigai Kohei
2005-12-03  4:38                                       ` KaiGai Kohei
2005-10-12  4:25                           ` Kaigai Kohei

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=430B260F.1070007@ak.jp.nec.com \
    --to=kaigai@ak.jp.nec.com \
    --cc=jmorris@namei.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.