From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q9UJjSla068591 for ; Tue, 30 Oct 2012 14:45:28 -0500 Date: Tue, 30 Oct 2012 14:47:18 -0500 From: Ben Myers Subject: Re: [PATCH] xfsdump:fill in bs_forkoff Message-ID: <20121030194718.GD405@sgi.com> References: <5080D0BD.3000304@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <5080D0BD.3000304@redhat.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Eric Sandeen Cc: xfs-oss Hey Eric, On Thu, Oct 18, 2012 at 11:02:05PM -0500, Eric Sandeen wrote: > Upstream, the structure containing bs_forkoff is actually zeroed > prior to these functions, but when pulling the patch back to an > older xfsdump, we got checksum errors due to an uninitialized > bs_forkoff not matching in dump vs. restore. > > So even though forkoff won't be explicitly restored from > a dump, do explicitly set it in these routines to keep checksums > happy. > > Signed-off-by: Eric Sandeen Would you say that this is appropriate for the upcoming release? Thanks, Ben _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs