xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: reproducible xfs/vmap oops

from [Christoph Hellwig] [Permanent Link][Original]
To: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
Subject: Re: reproducible xfs/vmap oops
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sun, 15 Feb 2009 14:15:25 -0500
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20090210075455.GA27111@xxxxxxxxxxxxx>
References: <20090201081224.GA22398@xxxxxxxxxxxxx> <200902042027.40762.nickpiggin@xxxxxxxxxxxx> <20090204193846.GA26436@xxxxxxxxxxxxx> <200902101543.15988.nickpiggin@xxxxxxxxxxxx> <20090210075455.GA27111@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17) 
Given how late we are in the 2.6.29 process we should probably revert
95f8e302c04c0b0c6de35ab399a5551605eeb006 and
d2859751cd0bf586941ffa7308635a293f943c17 and try again for 2.6.30.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  xfs: prevent kernel crash due to corrupted inode log format, Christoph Hellwig
Next by Date:  Re: [PATCH] Fix off by one error in page_region_mask(), Christoph Hellwig
Previous by Thread:  Re: reproducible xfs/vmap oops, Christoph Hellwig
Next by Thread:  Re: reproducible xfs/vmap oops, Dave Chinner
Indexes:  [Date] [Thread] [Top] [All Lists]