All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Nick Piggin <npiggin@kernel.dk>, xfs@oss.sgi.com
Subject: Re: XFS bad inode magic/vsn daddr 64 #8 (magic=5858)
Date: Thu, 21 Oct 2010 12:24:56 +1100	[thread overview]
Message-ID: <20101021012456.GA3459@amd> (raw)
In-Reply-To: <20101020151927.GA21057@infradead.org>

On Wed, Oct 20, 2010 at 11:19:27AM -0400, Christoph Hellwig wrote:
> On Wed, Oct 20, 2010 at 07:24:09PM +1100, Nick Piggin wrote:
> > Hi, I keep hitting this bug running xfstests, and managed to
> > reproduce it several times on current vanilla upstream kernel
> > too, below is one trace.
> > 
> > Nothing special about the xfstests run, except that it is run
> > on brd device for both the test and the scratch mounts. No
> > special mount options or mkfs flags. It seems pretty reproducable
> > though, triggering every time I've run the tests like this.
> > 
> > I didn't narrow down the test that causes the bug because it
> > keeps running other tests and then eventually hanging. Any hints
> > to narrow it down?
> 
> Care to check if it goes away if you remove the special casing of
> BLKFLSBUF in brd_ioctl?

Ah yes that stupid special case is probably causing other problems
even if not this crash. I'll try your suggestions when I start some more
tests running later today.

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

      parent reply	other threads:[~2010-10-21  1:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20  8:24 XFS bad inode magic/vsn daddr 64 #8 (magic=5858) Nick Piggin
2010-10-20 15:19 ` Christoph Hellwig
2010-10-20 15:22   ` Christoph Hellwig
2010-10-21  1:24   ` Nick Piggin [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=20101021012456.GA3459@amd \
    --to=npiggin@kernel.dk \
    --cc=hch@infradead.org \
    --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.