| To: | Alex Lyakas <alex@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_vm_releasepage() causing BUG at free_buffer_head() |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 20 Jul 2016 09:11:08 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <143E2E5E912B4C348E8C62AA987F0506@alyakaslap> |
| References: | <143E2E5E912B4C348E8C62AA987F0506@alyakaslap> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Mon, Jul 18, 2016 at 09:00:41PM +0300, 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)); XFS doesn't use the bh->b_assoc_buffers field at all, so nothing in XFS should ever corrupt it. Do you have any extN filesystems active, or any other filesystems/block devices that use bufferheads than might have a use after free bug? e.g. a long time ago (circa ~2.6.16, IIRC) we had a bufferhead corruption problem detected in XFS that was actually caused by a reiserfs use after free. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_vm_releasepage() causing BUG at free_buffer_head(), Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH 3/3] xfs: remove __arch_pack, Dave Chinner |
| Previous by Thread: | Re: xfs_vm_releasepage() causing BUG at free_buffer_head(), Dave Chinner |
| Next by Thread: | Re: xfs_vm_releasepage() causing BUG at free_buffer_head(), Alex Lyakas |
| Indexes: | [Date] [Thread] [Top] [All Lists] |