reproducible xfs/vmap oops

Christoph Hellwig hch at infradead.org
Tue Feb 3 09:51:47 CST 2009


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?




More information about the xfs mailing list