| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: XFS regression: Oops in xfs_buf_do_callbacks on xfstest 137 |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Fri, 17 Aug 2012 13:15:43 -0500 |
| In-reply-to: | <20120817180254.GA15382@xxxxxxxxxxxxx> |
| References: | <501ABC84.6030708@xxxxxxxxxxx> <20120817180254.GA15382@xxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 |
On 8/17/12 1:02 PM, Christoph Hellwig wrote: I'd be this is my new code added to xfs_buf_item_unpin, but I don't quite understand why. It's been a long time since I wrote that code, but I had to add that code to make sure we clear all buffers during a forced shutdown. Can you test if things go away if you just remove it (even if causes other hangs?) It does go away AFAIK, since the bisect found it. Sadly it's been on the back burner for me, under other deadline pressure. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS regression: Oops in xfs_buf_do_callbacks on xfstest 137, Christoph Hellwig |
|---|---|
| Next by Date: | Re: NULL pointer dereference in ext4_ext_remove_space on 3.5.1, Theodore Ts'o |
| Previous by Thread: | Re: XFS regression: Oops in xfs_buf_do_callbacks on xfstest 137, Christoph Hellwig |
| Next by Thread: | Re: xfs_growfs / planned resize / performance impact, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |