From: Mark Lord <kernel@teksavvy.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: GIT PULL] ext4 updates for 3.5
Date: Fri, 01 Jun 2012 12:45:27 -0400 [thread overview]
Message-ID: <4FC8F1A7.2060208@teksavvy.com> (raw)
In-Reply-To: <E1SaTSI-0005UV-4B@tytso-glaptop.cam.corp.google.com>
On 12-06-01 11:07 AM, Theodore Ts'o wrote:
> Ext4 updates for 3.5
>
> The major new feature added in this update is Darrick J. Wong's
> metadata checksum feature, which adds crc32 checksums to ext4's
> metadata fields. There is also the usual set of cleanups and bug
> fixes.
That sounds vaguely like an on-disk change that may have issues
with systems that regularly switch between older and newer kernel versions.
Could you elaborate on it a bit more, thanks!
next prev parent reply other threads:[~2012-06-01 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 15:07 GIT PULL] ext4 updates for 3.5 Theodore Ts'o
2012-06-01 15:44 ` Linus Torvalds
2012-06-01 17:19 ` Linus Torvalds
2012-06-01 17:43 ` Ted Ts'o
2012-06-01 17:56 ` Linus Torvalds
2012-06-01 16:45 ` Mark Lord [this message]
2012-06-01 17:53 ` Ted 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=4FC8F1A7.2060208@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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