Re: btrfs triggered lockdep WARN.

From: Chris Mason
Date: Thu Jun 27 2013 - 11:39:07 EST


Quoting Dave Jones (2013-06-27 11:19:22)
> On Thu, Jun 27, 2013 at 11:01:30AM -0400, Chris Mason wrote:
> > Quoting Dave Jones (2013-06-27 10:58:24)
> > > Another bug caused by this script. https://github.com/kernelslacker/io-tests/blob/master/setup.sh
> >
> > I'm still struggling to reproduce that one here. I've tried every
> > variation I can think of but I'll try again.
>
> Note that this is a different trace to the other post about that script.

Yeah, but I haven't hit anything unusual at all yet.

>
> > I really hope you don't already have CONFIG_DEBUG_PAGE_ALLOC turned on,
> > maybe it will catch this?
>
> I do. Though given this is lockdep complaining about what looks like
> memory corruption, it's probably not related.

Ok, could you please try this with some heavy memory pressure? I'm
hoping to trigger a use-after-free that points us in the right
direction.

-chris

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/