On Thu, Dec 10, 2015 at 02:02:20PM -0500, Chris Mason wrote:
> 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.
pretty easily yeah. I hit it maybe a couple dozen times yesterday.
So if you've got some idea of printk's to spray anywhere I can give
that a shot.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
