Re: Possible btrfs deadlock coused by commit 660d3f6c

2012-01-16 Thread Chris Samuel
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 -- To unsubscribe from this list: send the line "unsubscribe linux

Re: Possible btrfs deadlock coused by commit 660d3f6c

2012-01-16 Thread Josef Bacik
On Mon, Jan 16, 2012 at 08:45:29PM +, Al Viro wrote: > On Mon, Jan 16, 2012 at 09:26:00AM -0500, Josef Bacik wrote: > > On Mon, Jan 16, 2012 at 09:53:23AM +0100, Stanislaw Gruszka wrote: > > > Hi Josef, > > > > > > commit 660d3f6cde552323578b85fc5a09a6742f1fe804 > > > Author: Josef Bacik > >

Re: Possible btrfs deadlock coused by commit 660d3f6c

2012-01-16 Thread Al Viro
On Mon, Jan 16, 2012 at 09:26:00AM -0500, Josef Bacik wrote: > On Mon, Jan 16, 2012 at 09:53:23AM +0100, Stanislaw Gruszka wrote: > > Hi Josef, > > > > commit 660d3f6cde552323578b85fc5a09a6742f1fe804 > > Author: Josef Bacik > > Date: Fri Dec 9 11:18:51 2011 -0500 > > > > Btrfs: fix how we

Re: Possible btrfs deadlock coused by commit 660d3f6c

2012-01-16 Thread Josef Bacik
On Mon, Jan 16, 2012 at 09:53:23AM +0100, Stanislaw Gruszka wrote: > Hi Josef, > > commit 660d3f6cde552323578b85fc5a09a6742f1fe804 > Author: Josef Bacik > Date: Fri Dec 9 11:18:51 2011 -0500 > > Btrfs: fix how we do delalloc reservations and how we free reservations > on error > > introd