public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: CAI Qian <caiqian@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: 3.9-rc2 xfs panic
Date: Tue, 12 Mar 2013 18:46:08 +1100	[thread overview]
Message-ID: <20130312074608.GL21651@dastard> (raw)
In-Reply-To: <1032405745.12626044.1363070047355.JavaMail.root@redhat.com>

On Tue, Mar 12, 2013 at 02:34:07AM -0400, CAI Qian wrote:
> 
> 
> ----- Original Message -----
> > From: "Dave Chinner" <david@fromorbit.com>
> > To: "CAI Qian" <caiqian@redhat.com>
> > Cc: xfs@oss.sgi.com
> > Sent: Tuesday, March 12, 2013 2:07:01 PM
> > Subject: Re: 3.9-rc2 xfs panic
> > 
> > On Tue, Mar 12, 2013 at 12:32:28AM -0400, CAI Qian wrote:
> > > Just came across when running xfstests using 3.9-rc2 kernel on a
> > > power7
> > > box with addition of this patch which fixed a known issue,
> > > http://people.redhat.com/qcai/stable/01-fix-double-fetch-hlist.patch
> > > 
> > > The log shows it was happened around test case 370 with
> > > TEST_PARAM_BLKSIZE = 2048
> > 
> > That doesn't sound like xfstests. it only has 305 tests, and no
> > parameters like TEST_PARAM_BLKSIZE....
> Sorry, it is a typo, test case 270 not 370. TEST_PARAM_BLKSIZE was
> from an internal wrapper to be used to create new filessytem not from the
> original xfstests.

OK, so that means you're testing 2k filesystem block size on a 64k
page size machine? Are you running with CONFIG_XFS_DEBUG=y?

> > So, looks like memory corruption - a corrupted slab, perhaps? Can
> > you turn on memory poisoning, debugging, etc?

Does this turn anything up?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2013-03-12  7:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1868681549.12603593.1363061997919.JavaMail.root@redhat.com>
2013-03-12  4:32 ` 3.9-rc2 xfs panic CAI Qian
2013-03-12  6:07   ` Dave Chinner
2013-03-12  6:34     ` CAI Qian
2013-03-12  7:46       ` Dave Chinner [this message]
2013-03-12  8:04         ` CAI Qian
2013-03-12 10:23           ` Dave Chinner
2013-03-13  2:44         ` CAI Qian
2013-03-13  4:43           ` Dave Chinner
2013-03-13  4:56             ` CAI Qian
2013-03-14  7:39             ` CAI Qian
2013-03-14  8:06               ` CAI Qian
2013-03-14 13:17                 ` Mark Tinguely
2013-03-14 23:39                   ` Dave Chinner
2013-03-28  8:39         ` CAI Qian

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=20130312074608.GL21651@dastard \
    --to=david@fromorbit.com \
    --cc=caiqian@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox