mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: "Theodore Ts'o" <tytso@mit.edu>, "Stephen C. Tweedie" <sct@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] [RFC] [PATCH 3/4] Add extended attributes to ext2/3
Date: Wed, 9 Oct 2002 13:29:28 +0200	[thread overview]
Message-ID: <200210091329.28153.agruen@suse.de> (raw)
In-Reply-To: <20021008221710.GA9842@think.thunk.org>

On Wednesday 09 October 2002 00:17, Theodore Ts'o wrote:
> On Tue, Oct 08, 2002 at 09:41:43PM +0100, Stephen C. Tweedie wrote:
> > On Tue, Oct 08, 2002 at 08:20:38PM +0100, Christoph Hellwig wrote:
> > > On Tue, Oct 08, 2002 at 09:14:00PM +0200, Andreas Gruenbacher wrote:
> > > > Users might just fill up all xattr space leaving no space for ACLs
> > > > (or similar). If user xattrs are disabled this can no longer occur,
> > > > so some administrators might be happy to have a choice.
> > >
> > > Umm, that's why we have quota..
> >
> > It's the per-inode extended attribute space that's at risk here,
> > quotas don't help.
>
> Well, how about this as a compromise?  We define a new superblock
> field which reserves a certain amount of space in the EA block for
> "system" attributes.  The default will be zero, but if we want to
> reserve space for the ACL, we can do that by adjusting the superblock
> field.  (I'll add support into tune2fs for that purpose.)
>
> I'll then remove the CONFIG #ifdef's and the user_xattr mount options.
> (I hate having too many mount options, and this sort of thing should
> be a per-filesystem run-time decision, not a compile-time option.)
>
> Andreas, does that sound good to you?

I'd rather not store such policy things on the file system permanently, and 
make it a mount option. I'm wondering how many installations this would 
affect; to me it seems that it's not worth a super block flag.

Eventually we will hopefully move to a more flexible xattr storage mechanism; 
that hack will then just become baggage.

--Andreas.


  reply	other threads:[~2002-10-09 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 18:08 tytso
2002-10-08 18:53 ` [Ext2-devel] " Christoph Hellwig
2002-10-08 19:14   ` Andreas Gruenbacher
2002-10-08 19:20     ` Christoph Hellwig
2002-10-08 20:41       ` Stephen C. Tweedie
2002-10-08 20:47         ` Christoph Hellwig
2002-10-08 21:19           ` Andreas Dilger
2002-10-08 22:17         ` Theodore Ts'o
2002-10-09 11:29           ` Andreas Gruenbacher [this message]
2002-10-09 15:25             ` Stephen C. Tweedie
2002-10-08 22:21   ` Theodore Ts'o
     [not found]     ` <20021009064242.GW3045@clusterfs.com>
2002-10-09 13:09       ` Christoph Hellwig

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=200210091329.28153.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=tytso@mit.edu \
    /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®