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 qAD1xptP010842 for ; Mon, 12 Nov 2012 19:59:51 -0600 Date: Mon, 12 Nov 2012 20:01:50 -0600 From: Ben Myers Subject: Re: [PATCH 0/3] xfs: fixes for 3.7-rc6 Message-ID: <20121113020150.GY9783@sgi.com> References: <1352718586-3538-1-git-send-email-david@fromorbit.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1352718586-3538-1-git-send-email-david@fromorbit.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: Dave Chinner Cc: xfs@oss.sgi.com Hi Dave, On Mon, Nov 12, 2012 at 10:09:43PM +1100, Dave Chinner wrote: > These are the remaining fixes I have in my tree for the 3.7 cycle. > One is a corruption fix, the other two are problems I'm seeing > during shutdown and recovery testing. That testing lasts 400-500 > cycles (3-4 hours) now before it fails with another, as yet unknown > buffer/perag reference assert failure. Without these fixes, it lasts > 3-4 cycles before assert failing or triggering a BUG. > > I'd like these fixes to be in the 3.7 cycle if at all possible, with > both patch 1 and 2 being stable kernel candidates. I think we can make that happen. I noticed that you posted patches 2 and 3 earlier today and had to chuckle, but I understand. We'll put this 3.7 work at the top of the priority queue, followed by your 3.8 queue, and then the few items left for the userspace release. Thanks for reposting your 3.8 queue, BTW. Sometimes I think that frequent reposts are inconvenient, but in this case I think it will be helpful. Thanks, Ben _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs