All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Reiserfs List <reiserfs-list@namesys.com>
Subject: ReiserFS XATTR/ACL on 2.5
Date: Thu, 12 Jun 2003 10:25:38 -0400	[thread overview]
Message-ID: <3EE88D62.6050602@suse.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hello all -

I previously posted that I have ported my xattr/acl patches from the 
SuSE kernel to the vanilla kernel. They were available for 2.4 only.

After receiving a few emails, I have forward ported the patches to 2.5.70.

 From the README:
    For the most part, these patches are identical to the patches for 
2.4. This means that there may well be locking and performance issues, 
but these are also the first release I've made against 2.5. I've done 
some basic stress testing (18h of stress.sh w/ a default ACL set), but 
beyond that, they're new to the world.

     The main difference is that, in contrast to Andreas' 2.4 patches, 
trusted and user xattrs are implied to be enabled if xattrs are enabled. 
Trusted xattrs, as before, are enabled at runtime if xattrs are compield 
in. User xattrs, as before, need to have the user_xattr mount option set.

     The original patches have been part of the SuSE kernel for some 
time, but haven't really seen testing on a vanilla kernel. Use at your 
own risk.

The patches are available at: 
ftp://ftp.suse.com/pub/people/jeffm/reiserfs/aclea/2.5.70

-Jeff

-- 
jeffm@suse.com
jeffm@csh.rit.edu

[-- Attachment #2: Type: application/pgp-signature, Size: 252 bytes --]

                 reply	other threads:[~2003-06-12 14:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3EE88D62.6050602@suse.com \
    --to=jeffm@suse.com \
    --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.