All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Brian Foster <bfoster@redhat.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] Re: XFS: Assertion failed: first <= last && last < BBTOB(bp->b_length), file: fs/xfs/xfs_trans_buf.c, line: 568
Date: Tue, 27 Aug 2013 08:04:56 -0500	[thread overview]
Message-ID: <521CA3F8.7070805@sgi.com> (raw)
In-Reply-To: <521BC64A.6040005@sgi.com>

On 08/26/13 16:19, Mark Tinguely wrote:
> On 08/26/13 16:04, Dave Chinner wrote:
>> On Mon, Aug 26, 2013 at 10:00:24AM -0500, Mark Tinguely wrote:
>>> On 08/26/13 08:36, Brian Foster wrote:
>>>> On 08/26/2013 12:13 AM, Dave Chinner wrote:
>>>>> On Thu, Aug 22, 2013 at 02:28:00PM -0400, Brian Foster wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I hit an assert on a debug kernel while beating on some finobt
>>>>>> work and
>>>>>> eventually reproduced it on unmodified/TOT xfs/xfsprogs as of
>>>>>> today. I
>>>>>> hit it through a couple different paths, first while running
>>>>>> fsstress on
>>>>>> a CRC enabled filesystem (with otherwise default mkfs options):
>>>>>>
>>>>>> (These tests are running on a 4p, 4GB VM against a 100GB virtio disk,
>>>>>> hosted on a single spindle desktop box).
>>>>>>
>>>>>> crc=1
>>>>>> fsstress -z -fsymlink=1 -n99999999 -p4 -d /mnt/test
>>>>>>
>>>>>> XFS: Assertion failed: first<= last&& last< BBTOB(bp->b_length),
>>>>>
>>>>> Directory buffer overrun.

> A full test still asserts on the remove with the patched Linux 3.10 - I
> am about 50% into the retest of Linux 3.10 and then I was planning to
> move back to Linux 3.9.
>
> kdump did not work, so I have no vmcore and therefore no productive
> information.
>

Confirmed the Linux 3.10 asserts. Linux 3.9 does not assert.

I will fix the kdump and try to catch a Linux 3.10 assert.

--Mark.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-08-27 13:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 18:28 XFS: Assertion failed: first <= last && last < BBTOB(bp->b_length), file: fs/xfs/xfs_trans_buf.c, line: 568 Brian Foster
2013-08-23 13:18 ` Mark Tinguely
2013-08-23 13:30   ` Brian Foster
2013-08-23 13:57     ` Mark Tinguely
2013-08-23 16:49       ` Brian Foster
2013-08-23 18:01         ` Mark Tinguely
2013-08-26  4:13 ` [PATCH] " Dave Chinner
2013-08-26 13:36   ` Brian Foster
2013-08-26 15:00     ` Mark Tinguely
2013-08-26 21:04       ` Dave Chinner
2013-08-26 21:19         ` Mark Tinguely
2013-08-27 13:04           ` Mark Tinguely [this message]
2013-08-26 20:26   ` Michael L. Semon
2013-08-29 12:37   ` Mark Tinguely
2013-08-30 14:56     ` Ben Myers
2013-09-12 23:51 ` Mark Tinguely
2013-09-16 15:44   ` Christoph Hellwig
2013-09-16 17:30     ` Mark Tinguely
2013-09-16 17:41     ` Michael L. Semon

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=521CA3F8.7070805@sgi.com \
    --to=tinguely@sgi.com \
    --cc=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.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.