From: Theodore Ts'o <tytso@mit.edu>
To: Tao Ma <tm@tao.ma>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: RFC: remove CONFIG_EXT4_FS_XATTR
Date: Wed, 5 Dec 2012 22:48:42 -0500 [thread overview]
Message-ID: <20121206034842.GA21009@thunk.org> (raw)
In-Reply-To: <50BFF5D6.7050804@tao.ma>
On Thu, Dec 06, 2012 at 09:33:10AM +0800, Tao Ma wrote:
> To be frank, I didn't try the inline data test without xattr support. So
> that would be great if we remove it. :)
>
> btw, does any distribution disable xattr support during kernel build? As
> Eric said on behalf of redhat, and in my ubuntu box xattr is enabled.
> Would Jan confirm that SUSE also use it by default?
I'm pretty sure SuSE enables it, since SELinux requires it, and SuSE
supports it.
I'm more concerned with various embedded use cases, which is why I
measured how much additional text/data space xattr support enables
(which was only 27k, so I doubt that would be an issue in most
embedded use cases --- hmm.... I've just checked a Nexus 4 kernel
config and it enables CONFIG_FS_EXT4_XATTR; I'm not sure Android is
actually using xattrs at all at the moment, but it's certainly
enabled).
- Ted
next prev parent reply other threads:[~2012-12-06 3:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 22:35 RFC: remove CONFIG_EXT4_FS_XATTR Theodore Ts'o
2012-12-05 23:04 ` Eric Sandeen
2012-12-06 1:33 ` Tao Ma
2012-12-06 3:48 ` Theodore Ts'o [this message]
2012-12-06 19:28 ` David Brown
2012-12-06 10:26 ` Jan Kara
2012-12-10 6:19 ` [PATCH] ext4: Remove CONFIG_EXT4_FS_XATTR Tao Ma
2012-12-10 10:08 ` Jan Kara
2012-12-10 15:11 ` [PATCH V2] " Tao Ma
2012-12-10 19:21 ` [PATCH] " Theodore Ts'o
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=20121206034842.GA21009@thunk.org \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tm@tao.ma \
/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.