From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: 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: Tue, 8 Oct 2002 20:20:38 +0100 [thread overview]
Message-ID: <20021008202038.A15692@infradead.org> (raw)
In-Reply-To: <200210082114.00576.agruen@suse.de>; from agruen@suse.de on Tue, Oct 08, 2002 at 09:14:00PM +0200
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..
> With the registration API modules doing HSM/LSM/... can just register handlers
> without having to modify the file system code. Otherwise we would have to
> hand code additional hooks for independently loadable modules.
a) if the HSM/whatever is so standalone that it should patch ext2 code
it is truely generic and thus above the filesystem.
b) you don;t even export the register/unregister to modules, not mention
other ext2/ext3 core functionality that it would need.
c) looks at the 'would' there is no such code currently and if it gets
a real consern it still could be added. Don't bloat the kernel
more than you really need to..
next prev parent reply other threads:[~2002-10-08 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 18:08 [RFC] [PATCH 3/4] Add extended attributes to ext2/3 tytso
2002-10-08 18:53 ` [Ext2-devel] " Christoph Hellwig
2002-10-08 19:14 ` Andreas Gruenbacher
2002-10-08 19:20 ` Christoph Hellwig [this message]
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
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=20021008202038.A15692@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 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.