From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 2/2 V2] e2fsprogs: enable user namespace xattrs by default
Date: Sun, 20 Feb 2011 18:31:08 -0500 [thread overview]
Message-ID: <20110220233108.GB4001@thunk.org> (raw)
In-Reply-To: <4D5D9981.1020300@redhat.com>
On Thu, Feb 17, 2011 at 03:56:17PM -0600, Eric Sandeen wrote:
> User namespace xattrs are generally useful, and I think extN
> is the only filesystem requiring a special mount option to
> enable them, when xattrs are otherwise available. So this
> change sets that mount option into the defaults, via a
> mke2fs.conf option.
>
> Note that if xattrs are config'd off, this will lead to a
> mostly-harmless:
>
> EXT4-fs (sdc1): (no)user_xattr options not supported
>
> message at mount time...
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
You didn't run "make check" before submitting these patches. Please
do so in the future! :-)
I'll fix up the expected test commit results for these two commits.
- Ted
next prev parent reply other threads:[~2011-02-20 23:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 18:12 [PATCH 0/2] e2fsprogs: update mkfs defaults Eric Sandeen
2011-02-16 18:14 ` [PATCH 1/2] e2fsprogs: turn off enforced fsck intervals by default Eric Sandeen
2011-02-16 18:24 ` Lukas Czerner
2011-02-16 19:12 ` Amir Goldstein
2011-02-16 22:55 ` Ted Ts'o
2011-02-17 21:55 ` [PATCH 1/2 V2] " Eric Sandeen
2011-02-16 18:21 ` [PATCH 2/2] e2fsprogs: enable user namespace xattrs " Eric Sandeen
2011-02-16 19:15 ` Andreas Dilger
2011-02-16 19:27 ` Eric Sandeen
2011-02-16 21:49 ` Ted Ts'o
2011-02-16 21:53 ` Eric Sandeen
2011-02-16 22:56 ` Ted Ts'o
2011-02-16 22:58 ` Eric Sandeen
2011-02-16 23:01 ` Ted Ts'o
2011-02-17 21:56 ` [PATCH 2/2 V2] " Eric Sandeen
2011-02-20 23:31 ` Ted Ts'o [this message]
2011-02-21 17:00 ` Eric Sandeen
2011-02-16 22:12 ` [PATCH 0/2] e2fsprogs: update mkfs defaults Andreas Dilger
2011-02-16 22:37 ` Eric Sandeen
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=20110220233108.GB4001@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).