From: Chris Mason <clm@fb.com>
To: <dsterba@suse.cz>, Josh Boyer <jwboyer@fedoraproject.org>,
<jbacik@fb.com>, linux-btrfs <linux-btrfs@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: Btrfs lockdep with 3.15 merge window v3.14-751-g683b6c6f82a6
Date: Wed, 2 Apr 2014 15:43:45 -0400 [thread overview]
Message-ID: <533C6871.7060003@fb.com> (raw)
In-Reply-To: <20140402164709.GI29256@twin.jikos.cz>
On 04/02/2014 12:47 PM, David Sterba wrote:
> On Tue, Apr 01, 2014 at 06:23:11PM -0400, Josh Boyer wrote:
>> Below is a lockdep spew I have on a local VM running Linus' tree as of
>> this afternoon. The specific git commit is v3.14-751-g683b6c6f82a6.
>
>> [ 295.349016] CPU0 CPU1
>> [ 295.349016] ---- ----
>> [ 295.349016] lock(&found->groups_sem);
>> [ 295.349016] local_irq_disable();
>> [ 295.349016] lock(&delayed_node->mutex);
>> [ 295.349016] lock(&found->groups_sem);
>> [ 295.349016] <Interrupt>
>> [ 295.349016] lock(&delayed_node->mutex);
>
> Fixed by https://urldefense.proofpoint.com/v1/url?u=https://patchwork.kernel.org/patch/3894781/&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=R1vuFCUzlD4QksU2UH3APFiFgMVkwmMci%2Bktv%2BzqQnE%3D%0A&s=adbe2bfbb243d9781307cfff001f30c01afd35a32e0fb976ecca933ef4cebd26
>
I've got this lined up for my next pull as well. I sent early this
time, but more is going in.
-chris
prev parent reply other threads:[~2014-04-02 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 22:23 Btrfs lockdep with 3.15 merge window v3.14-751-g683b6c6f82a6 Josh Boyer
2014-04-02 16:47 ` David Sterba
2014-04-02 16:56 ` Josh Boyer
2014-04-02 19:35 ` Josh Boyer
2014-04-02 19:43 ` Chris Mason [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=533C6871.7060003@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=jwboyer@fedoraproject.org \
--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).