From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Samuel <chris@csamuel.org>
Subject: Re: Possible btrfs deadlock coused by commit 660d3f6c
Date: Tue, 17 Jan 2012 09:35:36 +1100
Message-ID: <4F14A638.7020903@csamuel.org>
References: <20120116085322.GB2105@redhat.com> <20120116142540.GB8265@dhcp231-144.rdu.redhat.com> <20120116204528.GP23916@ZenIV.linux.org.uk> <20120116220142.GA10418@dhcp231-144.rdu.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Patrick <ragamuffin@datacomm.ch>, linux-btrfs@vger.kernel.org
To: Josef Bacik <josef@redhat.com>
Return-path: <linux-btrfs-owner@vger.kernel.org>
In-Reply-To: <20120116220142.GA10418@dhcp231-144.rdu.redhat.com>
List-ID: <linux-btrfs.vger.kernel.org>

On 17/01/12 09:01, Josef Bacik wrote:

> Good point, either way it's been fixed.  Thanks,

Is it worth pushing that fix into the stable 3.2.x releases ?

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC