linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: corruption on 3.1.0-rc9-next-20111011+
Date: Mon, 17 Oct 2011 16:51:09 +0800	[thread overview]
Message-ID: <4E9BEC7D.8070904@tao.ma> (raw)
In-Reply-To: <20111017081036.GN30887@longonot.mountain>

Hi Dan,
On 10/17/2011 04:10 PM, Dan Carpenter wrote:
> On Mon, Oct 17, 2011 at 09:57:00AM +0300, Dan Carpenter wrote:
>> Hi list,
>>
>> I hit a sanity check in ext4_ext_insert_index() and my filesystem
>> went read only.
>>
> 
> Hm...  That's odd.  My netbook hit the same bug last night as well.
> It's running the same kernel version and config but compiled on a
> different system.  I don't know why it has the '+' char on the end of
> the version name.  Maybe it always does that for linux-next, because
> I don't have any patches applied.
> 
> I've left it with the readonly filesystem for now.
This is caused by the commit 4fd30c033. Sorry for the trouble and please
check the patch I just sent. It should resolve the warning.

Thanks
Tao

  parent reply	other threads:[~2011-10-17  8:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17  6:57 corruption on 3.1.0-rc9-next-20111011+ Dan Carpenter
2011-10-17  8:10 ` Dan Carpenter
2011-10-17  8:45   ` [PATCH] ext4: Check extent overflow with the right range Tao Ma
2011-10-17  9:10     ` Yongqiang Yang
2011-10-17 14:16     ` Ted Ts'o
2011-10-18  2:27       ` Tao Ma
2011-10-18 15:07         ` Ted Ts'o
2011-10-17  8:51   ` Tao Ma [this message]
2011-10-17  9:08     ` corruption on 3.1.0-rc9-next-20111011+ Dan Carpenter

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=4E9BEC7D.8070904@tao.ma \
    --to=tm@tao.ma \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    /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).