From: Jeff Mahoney <jeffm@suse.com>
To: Nikita Danilov <Nikita@namesys.com>
Cc: Dieter =?unknown-8bit?Q?N=FCtzel?= <Dieter.Nuetzel@hamburg.de>,
"Andreas Dilger" <adilger@turbolabs.com>,
"ReiserFS List" <reiserfs-list@namesys.com>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: [reiserfs-list] Re: [REISERFS TESTING] new patches on ftp.namesys.com: 2.4.15-pre7
Date: Wed, 21 Nov 2001 11:52:49 -0500 [thread overview]
Message-ID: <20011121115249.D17894@fury.csh.rit.edu> (raw)
In-Reply-To: <200111210110.fAL1Atc11275@beta.namesys.com> <20011121011655.M1308@lynx.no> <15355.31671.983925.611542@beta.reiserfs.com> <20011121102517Z281563-17408+16912@vger.kernel.org> <15355.39821.401925.96954@beta.reiserfs.com>
In-Reply-To: <15355.39821.401925.96954@beta.reiserfs.com>; from Nikita@namesys.com on Wed, Nov 21, 2001 at 03:18:21PM +0300
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 2269 bytes --]
On Wed, Nov 21, 2001 at 03:18:21PM +0300, Nikita Danilov wrote:
> Dieter Nützel writes:
> > PS Have you read about the latest ACL discussion on LKML?
>
> Yes, but Hans thinks we shouldn't do ACL reiserfs 3.x and concentrate on
> v4 in stead. You can try to persuade him though. Same for extended
> attributes.
I started to write ACL support based on Andreas Grünbacher's patches at
http://acl.bestbits.at a few months ago. Since there was no decided upon
format, I stopped development so that I wouldn't leave non-standard
filesystems in my wake. Once the ACL/EA format/API is finalized, I'll
probably continue development on it.
On a more technical note, adding a new item type, such as an
extended attribute item will cause problems for implementations that
don't know about them. An idea kicked around a few months ago was to
simply change the version string so that implementations that don't
know about ACL support can't mount the new version. "can't mount"
could conceivably be changed to "can only mount read-only", but certainly
not read-write, since non-solid items need special handling (every item
but stat data is non-solid).
This creates the following scenario:
* Versions that don't know about the new version string will
refuse to mount the fs.
* Versions that know about the new version, but don't implement support
will be read-only. This is because items get moved during balancing, even
to un-related items. Knowledge of the inside non-solid items is required
to move them around. So, even if there is a single ACL on the system, in
some deep directory, it could affect balancing (cause a panic).
* Versions that know about the new version, and implement support will
be read-write.
I see something along the lines of EXT2's compatibility matrix happening
here, but due to the inherent incompatibilities, this may not be a prime
candidate for 2.4 inclusion.
-Jeff
--
Jeff Mahoney | "Bill Gates is a monocle and a Persian cat away
jeffm@suse.com | from being the villain in a James Bond movie."
jeffm@csh.rit.edu | -- Dennis Miller
[-- Attachment #2: Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2001-11-21 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200111210110.fAL1Atc11275@beta.namesys.com>
2001-11-21 8:49 ` Nikita Danilov
2001-11-21 8:16 ` [reiserfs-list] " Andreas Dilger
2001-11-21 12:58 ` Ed Tomlinson
2001-11-21 23:30 ` Stuart Young
2001-11-21 10:02 ` Nikita Danilov
2001-11-21 10:24 ` Dieter Nützel
2001-11-21 12:18 ` Nikita Danilov
2001-11-21 16:52 ` Jeff Mahoney [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=20011121115249.D17894@fury.csh.rit.edu \
--to=jeffm@suse.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=Nikita@namesys.com \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--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 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®