All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tristan Ye <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2 crashes on xfstest 013
Date: Sat, 14 May 2011 21:35:26 +0800	[thread overview]
Message-ID: <4DCE851E.8090703@oracle.com> (raw)
In-Reply-To: <BANLkTikRdsPs00jKP4uFEOmArzcyqn8PKQ@mail.gmail.com>

On 05/14/2011 04:11 AM, Goldwyn Rodrigues wrote:
> Hi,
> 
> On Fri, May 13, 2011 at 12:02 PM, Sunil Mushran
> <sunil.mushran@oracle.com> wrote:
>>> On Thu, May 12, 2011 at 7:36 AM, Tristan Ye<tristan.ye@oracle.com>  wrote:
>>>>
>>>> Hi Goldwyn,
>>>>        The root cause was due to we didn't skip an existing hole
>>>> somewhere when
>>>> punching a hole, to speak more accurately, the bug occurs at the time
>>>> when we
>>>> removing a partial extent record(which also means the last extent record
>>>> to
>>>> remove), as a result, the hole-punching code attempts to remove more than
>>>> the
>>>> length of whole extent record, which leads to the failure of following
>>>> assert(fs/ocfs2/alloc.c):
>>>>
>>>> 5507         BUG_ON(cpos<  le32_to_cpu(rec->e_cpos) || trunc_range>
>>>>  rec_range);
>>>>
>>>>        Could you please make a verification against my coming patch, I
>>>> passed xfs's
>>>> 013 testcase with the patch;-)
>>>>
>>> Did you post this patch? ... or am I being impatient?
>>>
>> Yes, he posted it.
>>
>> http://oss.oracle.com/pipermail/ocfs2-devel/2011-May/008077.html
>>
> 
> Somehow, it did not reach my mailbox.
> The patch works for me. Thanks for patching up.

Glad that you finally got it and it successfully fix your issue up;)

> 
> Regards,

      reply	other threads:[~2011-05-14 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  2:13 [Ocfs2-devel] ocfs2 crashes on xfstest 013 Goldwyn Rodrigues
2011-05-12  8:13 ` Tristan Ye
2011-05-12 12:36 ` Tristan Ye
2011-05-13 13:28   ` Goldwyn Rodrigues
2011-05-13 17:02     ` Sunil Mushran
2011-05-13 20:11       ` Goldwyn Rodrigues
2011-05-14 13:35         ` Tristan Ye [this message]

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=4DCE851E.8090703@oracle.com \
    --to=tristan.ye@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.