xfs
[Top] [All Lists]

Re: [PATCH] Re: xfsdump-3.0.4 problems

To: Mario Bachmann <mbachman@xxxxxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Subject: Re: [PATCH] Re: xfsdump-3.0.4 problems
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 27 Aug 2010 21:40:55 +1000
In-reply-to: <20100827111820.GA9837@xxxxxxxxxxxxxxxxx>
References: <20100816182236.249a2a0f@xxxxxxxxxxx> <20100816223021.GL10429@dastard> <20100817083227.06e23889@xxxxxxxxxxx> <20100817071337.GN10429@dastard> <20100817095340.6b9ab8e2@xxxxxxxxxxx> <20100817090534.GP10429@dastard> <20100817114550.GQ10429@dastard> <20100827111820.GA9837@xxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
On Fri, Aug 27, 2010 at 01:18:20PM +0200, Iustin Pop wrote:
> On Tue, Aug 17, 2010 at 09:45:50PM +1000, Dave Chinner wrote:
> > My fault. I screwed up the btree lookup for the inode validation.
> > Can you test the patch below?
> 
> I just see that 2.6.35.4 has been released, but it doesn't include this
> fix (as far as I can see). Could it be send for inclusion into the next
> stable please (yes, it fixes the issue for me too).

The commit is now upstream, it had a "cc: stable@xxxxxxxxxx" in it,
so it should get automatically queued for inclusion in the next
stable kernel release. If I don't see it appear in Greg's stable
queue once he starts processing the commits for the next stable
release, I'll chase it up....

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>