From: Theodore Ts'o <tytso@mit.edu>
To: Tao Ma <tm@tao.ma>
Cc: linux-ext4@vger.kernel.org, "Darrick J. Wong" <djwong@us.ibm.com>
Subject: Re: [PATCH] ext4: Use s_csum_seed instead of i_csum_seed for xattr block csum.
Date: Sun, 2 Sep 2012 23:39:05 -0400 [thread overview]
Message-ID: <20120903033905.GC5066@thunk.org> (raw)
In-Reply-To: <5044208B.2080008@tao.ma>
On Mon, Sep 03, 2012 at 11:14:19AM +0800, Tao Ma wrote:
> Hi Ted,
> As the corresponding kernel change has been merged, can this patch be
> merged to the e2fsporgs also?
Hi Tao,
I folded your change into the metadata checksum patches before I
applied them to the next branch (and which is now included in the
master branch). So if you use the master/next branch, it should be
fully in sync with the kernel implementation of metadata checksum.
This was along with a number of other cleanups that I did to collapse
related patches before they got fully applied into e2fsprogs.
I have run xfstests with metadata checksum enabled in the kernel with
the development branch of e2fsprogs, and it passes, so I'm fairly
confident they are in sync.
One of the questions that we should consider in the near future is
when to cut a e2fsprogs 1.43 release. Things which we might want to
consider adding before we cut 1.43 include the changes to fully
support online resize for 64-bit file systems, and possibly the inline
data patches, if we are confident in the e2fsprogs changes and that
the format of inline data is ready to be cast into concrete.
Regards,
- Ted
next prev parent reply other threads:[~2012-09-03 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 14:13 [PATCH] ext4: Use s_csum_seed instead of i_csum_seed for xattr block csum Tao Ma
2012-06-26 2:23 ` Theodore Ts'o
2012-06-28 20:15 ` Darrick J. Wong
2012-06-29 2:27 ` Andreas Dilger
2012-06-29 18:13 ` Ted Ts'o
2012-06-30 14:19 ` Tao Ma
2012-07-09 14:12 ` Theodore Ts'o
2012-09-03 3:14 ` Tao Ma
2012-09-03 3:39 ` Theodore Ts'o [this message]
2012-09-03 5:37 ` Tao Ma
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=20120903033905.GC5066@thunk.org \
--to=tytso@mit.edu \
--cc=djwong@us.ibm.com \
--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 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).