xfs
[Top] [All Lists]

RE: XFS memory allocation deadlock in 2.6.38

To: "'Christoph Hellwig'" <hch@xxxxxxxxxxxxx>
Subject: RE: XFS memory allocation deadlock in 2.6.38
From: Sean Noonan <Sean.Noonan@xxxxxxxxxxxx>
Date: Tue, 22 Mar 2011 09:53:32 -0400
Accept-language: en-US
Acceptlanguage: en-US
Cc: "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx>, Martin Bligh <Martin.Bligh@xxxxxxxxxxxx>, Trammell Hudson <Trammell.Hudson@xxxxxxxxxxxx>, Stephen Degler <Stephen.Degler@xxxxxxxxxxxx>, Christos Zoulas <Christos.Zoulas@xxxxxxxxxxxx>
In-reply-to: <20110322100017.GA3532@xxxxxxxxxxxxx>
References: <081DDE43F61F3D43929A181B477DCA95639B52E8@xxxxxxxxxxxxxxxxxxxx> <20110322100017.GA3532@xxxxxxxxxxxxx>
Thread-index: Acvod/YLYcZN/knjQt6ixCf25YEgkAAFVM0w
Thread-topic: XFS memory allocation deadlock in 2.6.38
No, reverting this commit did not fix the issue.
We happened to have 2.6.36.1 and 2.6.37.2 available and tested against both of 
those.  I was not able to reproduce the bug with either version.

Sean

-----Original Message-----
From: Christoph Hellwig [mailto:hch@xxxxxxxxxxxxx] 
Sent: Tuesday, March 22, 2011 06:00
To: Sean Noonan
Cc: 'linux-xfs@xxxxxxxxxxx'; Martin Bligh; Trammell Hudson
Subject: Re: XFS memory allocation deadlock in 2.6.38

> We started testing with 2.6.38-rc7 and have seen this bug through to the .0 
> release.  This does not appear to be present in 2.6.33, but we have not done 
> testing in between.  We have tested with ext4 and do not encounter this bug.

Does reverting commit aea1b9532143218f8599ecedbbd6bfbf812385e1 fix the
issue for you?

<Prev in Thread] Current Thread [Next in Thread>