From: Dave Jones <davej@codemonkey.org.uk>
To: Josef Bacik <jbacik@fb.com>
Cc: Chris Mason <clm@fb.com>,
dsterba@suse.cz, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [4.1-rc7] btrfs related VM_BUG_ON in filemap.c
Date: Tue, 30 Jun 2015 15:28:44 -0400 [thread overview]
Message-ID: <20150630192844.GA2569@codemonkey.org.uk> (raw)
In-Reply-To: <5592EC94.2080002@fb.com>
On Tue, Jun 30, 2015 at 03:23:00PM -0400, Josef Bacik wrote:
> On 06/30/2015 03:20 PM, Dave Jones wrote:
> > On Wed, Jun 17, 2015 at 09:35:41AM -0400, Dave Jones wrote:
> >
> > > page:ffffea00027cc640 count:4 mapcount:0 mapping:ffff8800af11d8a0 index:0x0
> > > flags: 0x4000000000000846(error|referenced|active|private)
> > > page dumped because: VM_BUG_ON_PAGE(!PageLocked(page))
> > > ------------[ cut here ]------------
> > > kernel BUG at mm/filemap.c:745!
> >
> > Still occasionally bumping into this.
> > The 'count:4 mapcount:0' is constant in every instance I've seen
> > so far. Could that be a clue ?
> >
> > I've seen various page flags, but it's always !locked
> >
> > Ideas on additional debugging I could add ?
>
> Huh I just noticed that PG_Error seems to be set, is that the same for
> every time? I wonder where that's getting set and why. I'll dig into
> the areas we set that and see if I can spot anything. Thanks,
Seems to be set every time yeah.
I can try annotating those places that set it to see which one is triggering
when I get home.
Dave
prev parent reply other threads:[~2015-06-30 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 13:40 [4.1-rc7] btrfs related VM_BUG_ON in filemap.c Dave Jones
2015-06-10 17:43 ` Chris Mason
2015-06-10 18:42 ` Dave Jones
2015-06-16 17:14 ` David Sterba
2015-06-16 17:19 ` Chris Mason
2015-06-17 13:35 ` Dave Jones
2015-06-30 19:20 ` Dave Jones
2015-06-30 19:23 ` Josef Bacik
2015-06-30 19:28 ` Dave Jones [this message]
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=20150630192844.GA2569@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.