From: Wu Fengguang <fengguang.wu@intel.com>
To: Tao Ma <tm@tao.ma>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>
Subject: Re: ext4_ext_insert_index error
Date: Thu, 20 Oct 2011 10:07:27 +0800 [thread overview]
Message-ID: <20111020020727.GA11540@localhost> (raw)
In-Reply-To: <4E9F7F1E.8070809@tao.ma>
On Thu, Oct 20, 2011 at 09:53:34AM +0800, Tao Ma wrote:
> Hi Fengguang,
> sorry for the trouble.
That's fine.
> On 10/20/2011 09:23 AM, Wu Fengguang wrote:
> > Hi,
> >
> > I got these errors when switch the kernel from 3.1-rc8 to linux-next. Commit
> > 4fd30c0330ba951 looks most likely the culprit in the linux-next change set.
> This should be already fixed in Ted's tree. Please check whether the fix
> works.
> http://comments.gmane.org/gmane.comp.file-systems.ext4/28575
Glad to hear that, I'll try it.
Thanks,
Fengguang
next prev parent reply other threads:[~2011-10-20 2:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 1:23 ext4_ext_insert_index error Wu Fengguang
2011-10-20 1:53 ` Tao Ma
2011-10-20 2:07 ` Wu Fengguang [this message]
2011-10-20 3:48 ` Wu Fengguang
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=20111020020727.GA11540@localhost \
--to=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tm@tao.ma \
--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;
as well as URLs for NNTP newsgroup(s).