| To: | Nick Piggin <nickpiggin@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: reproducible xfs/vmap oops |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 3 Feb 2009 11:05:15 -0500 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <200902040303.13933.nickpiggin@xxxxxxxxxxxx> |
| References: | <20090201081224.GA22398@xxxxxxxxxxxxx> <20090201161458.GA5930@xxxxxxxxxxxxx> <20090203155147.GB21278@xxxxxxxxxxxxx> <200902040303.13933.nickpiggin@xxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Wed, Feb 04, 2009 at 03:03:13AM +1100, Nick Piggin wrote: > Hmm, seems similar to the other one Dave saw. I suppose it could > be due to bad parameters being passed to vmap API, but quite > likely it could be a bug in vmap as well. > > Any chance you can print out va_start and va_end from va and tmp > before going bug? (or if you like, I can try reproduce it with > xfsqa if there is a URL for it -- a quick google didn't help me). It's at http://git.kernel.org/?p=fs/xfs/xfstests-dev.git Right now I'm doing two verification runs with the current codebase and just that patch reverted as a second verification. After that I can do a patch with the debug printks. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: reproducible xfs/vmap oops, Christoph Hellwig |
|---|---|
| Next by Date: | [XFS updates] XFS development tree branch, mainline, updated. v2.6.28-rc3-12440-gb1792e3, xfs |
| 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] |