From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: bo.li.liu@oracle.com
Cc: LKML <linux-kernel@vger.kernel.org>, linux-btrfs@vger.kernel.org
Subject: Re: master - btrfs lockdep splat
Date: Thu, 12 Jan 2017 20:37:19 +0100 [thread overview]
Message-ID: <1484249839.4987.17.camel@gmail.com> (raw)
In-Reply-To: <20170112184427.GB24433@localhost.localdomain>
On Thu, 2017-01-12 at 10:44 -0800, Liu Bo wrote:
> On Thu, Jan 12, 2017 at 07:12:12PM +0100, Mike Galbraith wrote:
> > Greetings,
> >
> > I wanted to do some -rt testing, but seems non-rt kernels aren't
> > lockdep clean with btrfs /, making -rt testing a bit premature.
> >
> > (hm, 28a235931 Btrfs: fix lockdep warning on deadlock against an inode's log mutex)
>
> It's rather a false-positive lockdep warning than a real deadlock, and a
> patch[1] has been queued to fix it.
(yeah, just stops lockdep from perhaps finding something real)
> [1]: https://patchwork.kernel.org/patch/9473431/
Yup, virtual box seems to be a happy camper now. Thanks.
-Mike
prev parent reply other threads:[~2017-01-12 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:12 master - btrfs lockdep splat Mike Galbraith
2017-01-12 18:44 ` Liu Bo
2017-01-12 19:37 ` Mike Galbraith [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=1484249839.4987.17.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bo.li.liu@oracle.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).