xfs
[Top] [All Lists]

Re: [PATCH] Re: Corrupted XFS log replay oops.

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH] Re: Corrupted XFS log replay oops.
From: Felix Blyakher <felixb@xxxxxxx>
Date: Fri, 23 Jan 2009 00:20:44 -0600
Cc: Nick Piggin <nickpiggin@xxxxxxxxxxxx>, Eric Sesterhenn <snakebyte@xxxxxx>, Pavel Machek <pavel@xxxxxxx>, Chris Mason <chris.mason@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, npiggin@xxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20090123000617.GB4970@xxxxxxxxxxxxx>
References: <20090113142147.GE16333@alice> <20090120173455.GC21339@alice> <20090121035703.GH10158@disturbed> <200901211503.07308.nickpiggin@xxxxxxxxxxxx> <20090122043747.GU10158@disturbed> <20090122061158.GA31104@xxxxxxxxxxxxx> <20090123000203.GC32390@disturbed> <20090123000617.GB4970@xxxxxxxxxxxxx>

On Jan 22, 2009, at 6:06 PM, Christoph Hellwig wrote:

[XFS] Check buffer lengths in log recovery

Before trying to obtain, read or write a buffer,
check that the buffer length is actually valid. If
it is not valid, then something read in the recovery
process has been corrupted and we should abort
recovery.

Reported-by: Eric Sesterhenn <snakebyte@xxxxxx>
Signed-off-by: Dave Chinner <david@xxxxxxxxxxxxx>
Tested-by: Eric Sesterhenn <snakebyte@xxxxxx>


Reviewed-by: Christoph Hellwig <hch@xxxxxx>

Reviewed-by: Felix Blyakher <felixb@xxxxxxx>


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