From: Dave Jones <davej@redhat.com>
To: Chris Mason <chris.mason@fusionio.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs triggered lockdep WARN.
Date: Thu, 27 Jun 2013 13:03:12 -0400 [thread overview]
Message-ID: <20130627170312.GA17728@redhat.com> (raw)
In-Reply-To: <20130627153857.14981.14731@localhost.localdomain>
On Thu, Jun 27, 2013 at 11:38:57AM -0400, Chris Mason wrote:
> > > 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.
Have anything in particular in mind ? I tried a make -j on a kernel tree
in a loop, but nothing new is shaking out.
Dave
next prev parent reply other threads:[~2013-06-27 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 14:58 btrfs triggered lockdep WARN Dave Jones
2013-06-27 15:01 ` Chris Mason
2013-06-27 15:19 ` Dave Jones
2013-06-27 15:38 ` Chris Mason
2013-06-27 17:03 ` Dave Jones [this message]
2013-06-27 17:00 ` Josef Bacik
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=20130627170312.GA17728@redhat.com \
--to=davej@redhat.com \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).