From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: reproducible xfs/vmap oops
Date: Tue, 3 Feb 2009 10:51:47 -0500 [thread overview]
Message-ID: <20090203155147.GB21278@infradead.org> (raw)
In-Reply-To: <20090201161458.GA5930@infradead.org>
On Sun, Feb 01, 2009 at 11:14:58AM -0500, Christoph Hellwig wrote:
> On Sun, Feb 01, 2009 at 03:12:24AM -0500, Christoph Hellwig wrote:
> > When running xfsqa on the current xfs development tree (sometimes two
> > runs are needed to trigger it) I get the following oops. This seems to
> > have been introduced by the last mainling merge (with
> > 5ee810072175042775e39bdd3eaaa68884c27805), but I'd need to bisect it to
> > make sure my gut feeling is right.
>
> Still happens with a commit before that mainline merge. Looking for
> a good candiate for bisection now.
I bisected it down to commit 0087167c9d5b1273e7e6bbe39a9ab13bdb9a39bb
"[XFS] use scalable vmap API".
Nick, any idea what this could be?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-03 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 8:12 reproducible xfs/vmap oops Christoph Hellwig
2009-02-01 16:14 ` Christoph Hellwig
2009-02-03 15:51 ` Christoph Hellwig [this message]
[not found] ` <200902040303.13933.nickpiggin@yahoo.com.au>
2009-02-03 16:05 ` Christoph Hellwig
2009-02-03 18:44 ` Christoph Hellwig
2009-02-03 21:04 ` Christoph Hellwig
2009-02-03 21:42 ` Dave Chinner
2009-02-03 21:47 ` Christoph Hellwig
2009-02-03 22:08 ` Christoph Hellwig
[not found] ` <200902041648.55603.nickpiggin@yahoo.com.au>
2009-02-04 8:15 ` Christoph Hellwig
2009-02-04 8:30 ` Christoph Hellwig
[not found] ` <200902042027.40762.nickpiggin@yahoo.com.au>
2009-02-04 19:38 ` Christoph Hellwig
[not found] ` <200902101543.15988.nickpiggin@yahoo.com.au>
2009-02-10 7:54 ` Christoph Hellwig
2009-02-15 19:15 ` Christoph Hellwig
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=20090203155147.GB21278@infradead.org \
--to=hch@infradead.org \
--cc=nickpiggin@yahoo.com.au \
--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