[Top] [All Lists]

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

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>, Nick Piggin <nickpiggin@xxxxxxxxxxxx>, Eric Sesterhenn <snakebyte@xxxxxx>, Pavel Machek <pavel@xxxxxxx>, Chris Mason <chris.mason@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, npiggin@xxxxxxxxxxxx, xfs@xxxxxxxxxxx
Subject: Re: [PATCH] Re: Corrupted XFS log replay oops.
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 22 Jan 2009 19:06:17 -0500
In-reply-to: <20090123000203.GC32390@disturbed>
References: <20090113142147.GE16333@alice> <20090120173455.GC21339@alice> <20090121035703.GH10158@disturbed> <200901211503.07308.nickpiggin@xxxxxxxxxxxx> <20090122043747.GU10158@disturbed> <20090122061158.GA31104@xxxxxxxxxxxxx> <20090123000203.GC32390@disturbed>
User-agent: Mutt/1.5.18 (2008-05-17)
> [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>

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