From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Alex Lyakas <alex@zadarastorage.com>, xfs@oss.sgi.com
Subject: Re: xfs_vm_releasepage() causing BUG at free_buffer_head()
Date: Mon, 18 Jul 2016 22:18:36 +0200 [thread overview]
Message-ID: <578D399C.1010006@applied-asynchrony.com> (raw)
In-Reply-To: <143E2E5E912B4C348E8C62AA987F0506@alyakaslap>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-07-18 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 18:00 xfs_vm_releasepage() causing BUG at free_buffer_head() Alex Lyakas
2016-07-18 20:18 ` Holger Hoffstätte [this message]
2016-07-19 8:43 ` Alex Lyakas
2016-07-19 11:24 ` Holger Hoffstätte
2016-07-19 23:05 ` Dave Chinner
2016-07-19 23:11 ` Dave Chinner
2016-07-20 9:42 ` Alex Lyakas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=578D399C.1010006@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=alex@zadarastorage.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox