From: Andreas Dilger <adilger@clusterfs.com>
To: Russell Coker <bofh@coker.com.au>
Cc: ReiserFS <reiserfs-list@namesys.com>
Subject: Re: extended attributes
Date: Wed, 23 Oct 2002 19:45:23 -0600 [thread overview]
Message-ID: <20021024014522.GD28822@clusterfs.com> (raw)
In-Reply-To: <200210231916.18976.bofh@coker.com.au>
On Oct 23, 2002 19:16 +0200, Russell Coker wrote:
> Extended attribute support is apparently in 2.5.x kernels now and will be in
> 2.4.20.
>
> When will ReiserFS support extended attributes?
>
> Currently there is discussion about the possibility of using extended
> attributes for SE Linux security context labels, if that goes ahead then I
> will be forced to cease using any file system that lacks such support.
>
> I would like to continue using ReiserFS...
I would think that it would be practical to just store the EA data as a
separate file internally, if you are using tail packing. That avoids
the need to have a separate data format for EAs entirely.
What I would probably do is have an EA pointer from each inode. It
would just point to a directory and the EAs would be files with the
filename == attribute name. You can probably do special packing so
that this is stored efficiently...
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-10-24 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 17:16 extended attributes Russell Coker
2002-10-24 1:36 ` Hans Reiser
2002-10-24 2:50 ` Manuel Krause
2002-10-24 3:05 ` Hans Reiser
2002-10-24 1:45 ` Andreas Dilger [this message]
2002-10-24 13:05 ` Chris Mason
2002-10-24 13:12 ` Russell Coker
2002-11-18 21:32 ` Jeff Mahoney
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=20021024014522.GD28822@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=bofh@coker.com.au \
--cc=reiserfs-list@namesys.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 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.