| To: | Alex Lyakas <alex@xxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfs_vm_releasepage() causing BUG at free_buffer_head() |
| From: | Holger HoffstÃtte <holger@xxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Mon, 18 Jul 2016 22:18:36 +0200 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <143E2E5E912B4C348E8C62AA987F0506@alyakaslap> |
| Organization: | Applied Asynchrony, Inc. |
| References: | <143E2E5E912B4C348E8C62AA987F0506@alyakaslap> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 |
On 07/18/16 20:00, Alex Lyakas wrote: > Greetings XFS community, > > We have hit the following BUG [1]. > > This is in free_buffer_head(): > BUG_ON(!list_empty(&bh->b_assoc_buffers)); > > This is happening in a long-term mainline kernel 3.18.19. > > Some googling revealed a possibly-related discussion at: > http://comments.gmane.org/gmane.linux.file-systems/105093 > https://lkml.org/lkml/2016/5/30/1007 > except that in our case I don't see the "WARN_ON_ONCE(delalloc)" triggered. Since you make it past the WARN_ONs that makes it look like this very recent report from Friday: http://oss.sgi.com/pipermail/xfs/2016-July/050199.html Dave posted a patch in that thread which seems ot work fine and so far hasn't set anything on fire, at least for me on 4.4.x. cheers, Holger |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Metadata corruption detected at xfs_agf block, Eric Sandeen |
|---|---|
| Next by Date: | [4.7-rc6 snapshot] xfstests::generic/081 unable to tear down snapshot VG, Dave Chinner |
| Previous by Thread: | xfs_vm_releasepage() causing BUG at free_buffer_head(), Alex Lyakas |
| Next by Thread: | Re: xfs_vm_releasepage() causing BUG at free_buffer_head(), Alex Lyakas |
| Indexes: | [Date] [Thread] [Top] [All Lists] |