From: Chris Mason <clm@fb.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: <jbacik@fb.com>, <dsterba@suse.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: !PageLocked BUG_ON hit in clear_page_dirty_for_io
Date: Thu, 10 Dec 2015 14:02:20 -0500 [thread overview]
Message-ID: <20151210190220.GA11257@ret.masoncoding.com> (raw)
In-Reply-To: <20151209042528.GA2413@codemonkey.org.uk>
On Tue, Dec 08, 2015 at 11:25:28PM -0500, Dave Jones wrote:
> Not sure if I've already reported this one, but I've been seeing this
> a lot this last couple days.
>
> kernel BUG at mm/page-writeback.c:2654!
> invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC KASAN
> CPU: 1 PID: 2566 Comm: trinity-c1 Tainted: G W 4.4.0-rc4-think+ #14
> task: ffff880462811b80 ti: ffff8800cd808000 task.ti: ffff8800cd808000
> RIP: 0010:[<ffffffff8826ff40>] [<ffffffff8826ff40>] clear_page_dirty_for_io+0x180/0x1d0
Huh, are you able to reproduce at will? From this code path it should
mean somebody else is unlocking a page they don't own.
-chris
next prev parent reply other threads:[~2015-12-10 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 4:25 !PageLocked BUG_ON hit in clear_page_dirty_for_io Dave Jones
2015-12-10 15:09 ` Markus Trippelsdorf
2015-12-10 19:02 ` Chris Mason [this message]
2015-12-10 19:35 ` Dave Jones
2015-12-10 21:30 ` Chris Mason
2015-12-10 21:35 ` Liu Bo
2015-12-10 21:51 ` Filipe Manana
2015-12-10 22:57 ` Dave Jones
2015-12-11 3:59 ` Dave Jones
2015-12-10 23:58 ` Dave Jones
2015-12-10 20:42 ` Georg Lukas
2015-12-15 0:03 ` Chris Mason
2015-12-15 1:33 ` Liu Bo
2015-12-15 19:36 ` Filipe Manana
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=20151210190220.GA11257@ret.masoncoding.com \
--to=clm@fb.com \
--cc=davej@codemonkey.org.uk \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox