Re: reproducible xfs/vmap oops

Christoph Hellwig
2009-02-01T16:16:11Z

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.