public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
	akpm@osdl.org
Subject: Re: I oppose Chris and Jeff's patch to add an unnecessary	additional namespace to ReiserFS
Date: Mon, 26 Apr 2004 15:13:03 -0400	[thread overview]
Message-ID: <1083006783.30344.102.camel@watt.suse.com> (raw)
In-Reply-To: <408D51C4.7010803@namesys.com>

On Mon, 2004-04-26 at 14:15, Hans Reiser wrote:
> Chris Mason wrote:
> 
> >On Mon, 2004-04-26 at 12:59, Hans Reiser wrote:
> >
> >v4 didn't factor into these decisions because it was still in extremely
> >early stages back then (2.4.16 or so). 
> >
> It was clearly indicated then that accessing acls was scheduled for V4 
> not V3. 
> 
Well, that part we've always disagreed most on is how to support
existing users.  SUSE implemented the acls for v3 because we felt they
were an important feature, and didn't want to tell users asking for ACLs
to switch filesystems when it was reasonable to implement in v3.

It seems that you don't want the ACLs in v3 for two major reasons:

1) it's not v4
2) it's based on xattrs

I don't feel this is a good way to support v3, since v4 still means
telling someone to switch just for acls, and not using xattrs means not
using the same API as the rest of the kernel.

I hope v4 does improve the xattr api, and I hope it manages to do so for
more then just reiser4.  It is important that application writers are
able to code to a single interface and get coverage across all the major
linux filesystems.

-chris



  parent reply	other threads:[~2004-04-26 19:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 19:54 [PATCH] reiserfs v3 patches for 2.6.6-rc2 Chris Mason
2004-04-26 16:59 ` I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS Hans Reiser
2004-04-26 17:31   ` Chris Mason
2004-04-26 18:15     ` Hans Reiser
2004-04-26 19:12       ` Mark Hahn
2004-04-26 19:13       ` Chris Mason [this message]
2004-04-26 20:40         ` Matthias Andree
2004-04-26 22:20           ` Chris Wright
2004-04-26 23:20           ` Andrew Morton
2004-04-27 17:35           ` Hans Reiser
2004-04-27 18:00       ` Markus   Törnqvist
2004-04-26 19:33   ` Christoph Hellwig
2004-04-27 17:29     ` Hans Reiser
2004-04-27 17:34       ` Christoph Hellwig
2004-04-27 17:58         ` Hans Reiser
2004-04-27 18:04           ` Christoph Hellwig
2004-04-28  0:10             ` Stefan Traby
2004-04-27 18:07           ` Jeff Garzik
2004-04-28  5:51           ` Meelis Roos
2004-04-30 16:14           ` David Masover
2004-05-02  4:14           ` Rob Landley
2004-04-26 19:56   ` Matt H.

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=1083006783.30344.102.camel@watt.suse.com \
    --to=mason@suse.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=torvalds@osdl.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