| To: | xfs@xxxxxxxxxxx, Nick Piggin <nickpiggin@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: reproducible xfs/vmap oops |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 3 Feb 2009 10:51:47 -0500 |
| In-reply-to: | <20090201161458.GA5930@xxxxxxxxxxxxx> |
| References: | <20090201081224.GA22398@xxxxxxxxxxxxx> <20090201161458.GA5930@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
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? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_force_shutdown after Raid crash, Christoph Hellwig |
|---|---|
| Next by Date: | Re: reproducible xfs/vmap oops, Christoph Hellwig |
| Previous by Thread: | Re: reproducible xfs/vmap oops, Christoph Hellwig |
| Next by Thread: | Re: reproducible xfs/vmap oops, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |