From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n11GGAhU194122 for ; Sun, 1 Feb 2009 10:16:11 -0600 Received: from bombadil.infradead.org (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 7258BD5983 for ; Sun, 1 Feb 2009 08:15:29 -0800 (PST) Received: from bombadil.infradead.org (bombadil.infradead.org [18.85.46.34]) by cuda.sgi.com with ESMTP id a5t077v41DIRQGrX for ; Sun, 01 Feb 2009 08:15:29 -0800 (PST) Date: Sun, 1 Feb 2009 11:14:58 -0500 From: Christoph Hellwig Subject: Re: reproducible xfs/vmap oops Message-ID: <20090201161458.GA5930@infradead.org> References: <20090201081224.GA22398@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20090201081224.GA22398@infradead.org> 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: xfs@oss.sgi.com, Nick Piggin On Sun, Feb 01, 2009 at 03:12:24AM -0500, Christoph Hellwig wrote: > When running xfsqa on the current xfs development tree (sometimes two > runs are needed to trigger it) I get the following oops. This seems to > have been introduced by the last mainling merge (with > 5ee810072175042775e39bdd3eaaa68884c27805), but I'd need to bisect it to > make sure my gut feeling is right. Still happens with a commit before that mainline merge. Looking for a good candiate for bisection now. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs