[Top] [All Lists]

Re: [PATCH 4/4] V2 xfs: fix deadlock in xfs_rtfree_extent with kernel v2

To: Kamal Dasu <kdasu.kdev@xxxxxxxxx>
Subject: Re: [PATCH 4/4] V2 xfs: fix deadlock in xfs_rtfree_extent with kernel v2.6.37
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 28 Feb 2012 03:36:38 -0500
Cc: xfs@xxxxxxxxxxx
In-reply-to: <33390983.post@xxxxxxxxxxxxxxx>
References: <33390983.post@xxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Sat, Feb 25, 2012 at 07:57:02AM -0800, Kamal Dasu wrote:
> Christoph,
> I have not been able to create a simple test case for this yet.
> Currently the only way I have is to use an a time shift recording
> application 
> that stores video streams on a real-time subvolume.  Sometimes when such
> a stream is deleted I see the problem. I have not  figured out how to create
> a 
> test to consistently get allocation where the bit map span multiple extents
> while 
> freeing  the inode. 
> I am still trying to come with a simple test case. 
> If you have any ideas let me know I will be happy to try it out.
> I have also posted a equivalent post for the 3.3 kernel branch.
> http://old.nabble.com/-PATCH--xfs%3A-fix-deadlock-in-xfs_rtfree_extent-with-kernel-v3.x-to33375114.html

That's the mail I replied to :)

Either way - I'd love to get a good test case for it eventually, but for
now let's put in the obvious fix even if we don't have a good

Alex, I'd suggest this is a 3.3-rc issue as it's a regression, even if
an old one.

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