From: Ted Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Jan Kara <jack@suse.cz>,
Masayoshi MIZUMA <m.mizuma@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] [RESEND] ext3: set i_extra_isize of 11th inode
Date: Wed, 25 Aug 2010 21:21:17 -0400 [thread overview]
Message-ID: <20100826012117.GP4453@thunk.org> (raw)
In-Reply-To: <6B0D8B5D-C576-4DC2-B390-9D1EB8B6A5BA@dilger.ca>
On Wed, Aug 25, 2010 at 06:55:49PM -0600, Andreas Dilger wrote:
>
> I think you are missing the point. I don't think it matters which
> mke2fs is in use. The problem is that ext3_iget() has a workaround
> for this 5-year-old mke2fs bug that is actively causing a loss of
> xattr data if lost+found is reallocated.
Ah, OK. But it's still the case that the right answer at this point
is to make ext3 code conform to ext4, and drop the workaround
altogether.
- Ted
next prev parent reply other threads:[~2010-08-26 1:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 2:20 [PATCH] ext3: set i_extra_isize of 11th inode Masayoshi MIZUMA
2010-08-20 7:42 ` Andreas Dilger
2010-08-23 0:16 ` Masayoshi MIZUMA
2010-08-23 0:50 ` [PATCH] [RESEND] " Masayoshi MIZUMA
2010-08-24 13:17 ` Jan Kara
2010-08-25 0:05 ` Masayoshi MIZUMA
2010-08-25 23:04 ` Jan Kara
2010-08-25 23:39 ` Andreas Dilger
2010-08-26 0:36 ` Ted Ts'o
2010-08-26 0:55 ` Andreas Dilger
2010-08-26 1:21 ` Ted Ts'o [this message]
2010-08-26 1:51 ` Andreas Dilger
2010-08-26 1:25 ` Masayoshi MIZUMA
2010-08-26 12:27 ` Jan Kara
2010-08-26 23:59 ` Andreas Dilger
2010-08-27 13:58 ` Jan Kara
2010-08-27 18:57 ` Andreas Dilger
2010-09-09 16:38 ` Jan Kara
2010-09-09 19:23 ` Andreas Dilger
2010-08-26 0:26 ` Masayoshi MIZUMA
2010-08-26 12:29 ` Jan Kara
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=20100826012117.GP4453@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=m.mizuma@jp.fujitsu.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).