From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S964920AbVLQDbP@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S964920AbVLQDbP (ORCPT <rfc822;willy@w.ods.org>);
	Fri, 16 Dec 2005 22:31:15 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964913AbVLQDbP
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 16 Dec 2005 22:31:15 -0500
Received: from solarneutrino.net ([66.199.224.43]:57862 "EHLO
	tau.solarneutrino.net") by vger.kernel.org with ESMTP
	id S1751364AbVLQDbO (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 16 Dec 2005 22:31:14 -0500
Date: Fri, 16 Dec 2005 22:31:06 -0500
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Hugh Dickins <hugh@veritas.com>,
       Kai Makisara <Kai.Makisara@kolumbus.fi>, Andrew Morton <akpm@osdl.org>,
       linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
       ryan@tau.solarneutrino.net
Subject: Re: Fw: crash on x86_64 - mm related?
Message-ID: <20051217033106.GB20539@tau.solarneutrino.net>
References: <Pine.LNX.4.61.0512062025230.28217@goblin.wat.veritas.com> <20051206204336.GA12248@tau.solarneutrino.net> <Pine.LNX.4.61.0512071803300.2975@goblin.wat.veritas.com> <20051212165443.GD17295@tau.solarneutrino.net> <Pine.LNX.4.64.0512120928110.15597@g5.osdl.org> <1134409531.9994.13.camel@mulgrave> <Pine.LNX.4.64.0512121007220.15597@g5.osdl.org> <1134411882.9994.18.camel@mulgrave> <20051215190930.GA20156@tau.solarneutrino.net> <1134705703.3906.1.camel@mulgrave>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <1134705703.3906.1.camel@mulgrave>
User-Agent: Mutt/1.5.9i
From: Ryan Richter <ryan@tau.solarneutrino.net>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Dec 15, 2005 at 08:01:43PM -0800, James Bottomley wrote:
> On Thu, 2005-12-15 at 14:09 -0500, Ryan Richter wrote:
> > On Mon, Dec 12, 2005 at 12:24:42PM -0600, James Bottomley wrote:
> > > I'll find a fix for the real problem, but this patch isn't the cause.
> > 
> > Is the patch set you posted yesterday supposed to fix this?  If so, is
> > it available in patch form anywhere?
> 
> No, I've been too busin integrating other people's patches to work on
> ones of my own.  Try this.

Thanks for the patch, I'm testing it now.  If this survives the next few
days I'll leave it running while I'm away, otherwise testing will have
to wait until the new year.

Cheers,
-ryan